4 Replies Latest reply: Oct 29, 2012 12:26 PM by Branchbird - Pat RSS

    Where are the jvm min and max sizes set?

    953835
      Guess I should know this. EAC, Workbench, dgraph - were are the minimum and maximum sizes of these jvms set? I don't see them set up as part of the command line arguments.
      TIA

      Edited by: EndecaJoe on Oct 24, 2012 6:59 AM
        • 1. Re: Where are the jvm min and max sizes set?
          Pravin Chikhale
          You can increase the heap size for Workbench and PlatformServices in setenv.sh.
          You will find this files in
          *<Endeca_installation>/Workbench/<version>/server/bin*
          *<Endeca_installation>/PlatformServices/<version>/tools/server/bin*

          For EAC, you can provide heap size arguments in eaccmd.sh located at
          *<Endeca_installation>/PlatformServices/<version>/bin*

          HTH

          - Pravin.
          • 2. Re: Where are the jvm min and max sizes set?
            Branchbird - Pat
            You also mentioned the dgraph process, which is not a Java process so there is no jvm min/max.

            There is, however, the --cmem option which controls the size of the cache that the MDEX leverages to answer queries.

            Patrick
            • 3. Re: Where are the jvm min and max sizes set?
              953835
              And this points out how I am still confused.

              I am sure you are correct, but I see this when I do "ps"
              ... <>/apps/endeca/MDEX/6.2.2/bin/dgraph ...
              which is why I say "dgraph process".

              And on the first response I don't understand the differenece between PlatformServices or EAC. I always think of these as being the same.

              Edited by: EndecaJoe on Oct 29, 2012 5:44 AM
              • 4. Re: Where are the jvm min and max sizes set?
                Branchbird - Pat
                EndecaJoe wrote:
                And this points out how I am still confused.

                I am sure you are correct, but I see this when I do "ps"
                ... <>/apps/endeca/MDEX/6.2.2/bin/dgraph ...
                which is why I say "dgraph process".
                It is a process so it shows up in a ps command (or top, etc.) but it's not a Java process. The MDEX Engine is written in C++, not Java, and it runs in its own "container" unlike something such as the EAC which runs inside of Tomcat.
                And on the first response I don't understand the differenece between PlatformServices or EAC. I always think of these as being the same.
                Probably just a semantic difference. Platform Services includes the EAC among its components (another would be Forge) and is the software package you install. EAC is a part of that and it runs inside of a Tomcat container that is installed when you install Platform Services.

                Hope that helps...

                Patrick