...
- Java 1.8 changes the memory management in way that the JVM allocates heap space depending on the available physical memory (1/64).
- This results in the fact that JobScheduler tasks are allocated a lot of more memory than required. Typically such jobs, e.g. the JITL jobs, can be operated with 32 MB to 64 MB. However, for a server equipped with 64 GB physical memory each task will be allocated 1 GB by default.
- It is therefore recommended to reduce the memory consumption by JobScheduler settings, see chapter Modify heap size settings.
...
- The minimum memory allocation by Java can be checked with the command:
java -XX:+PrintFlagsFinal -version
The output of the command should provide a line that contains the stringInitialHeapSizewith the minimum heap space settingssetting.
- Java heap space usage can be modified by JobScheduler settings at job level and at a global level:
- The -Xmxsize parameter sets the maximum Java heap size
- The -Xmssize paramter sets the initial Java heap size
- each job can be assigned an attribute to e.g. specify 64 MB memory consumption like this
<job java_options="-Xmx64m -Xms64m"> - The file ./config/sos.ini can be used to specify the memory consumption for all jobs like this
[java]options = -Xmx64m-Xms64m - The file ./config/factory.ini can be used to specify memory consumption for jobs executed with Agents like this:
[java]job_options = -Xmx64m-Xms64m
- each job can be assigned an attribute to e.g. specify 64 MB memory consumption like this
- For more detailed information see How to increase or decrease the Java heap space
...