Additional Java memory tuning can be done on the application server in which Integration Server is ran. This helps reduce the memory footprint and wait times associated with garbage collection events.
For more information, refer to the Garbage-First Garbage Collector section in the Java Platform, Standard Edition HotSpot Virtual Machine Garbage Collection Tuning Guide. This has details about the internals of the collector and the different configuration parameters available when this garbage collector is being used.
The following Java options (JAVA_OPTS) must be specified as a starting point when tuning the JVM garbage collector for Integration Server.
| Parameter with recommend value | Description |
|---|---|
| -XX:+UseG1GC | Enables the Garbage First (G1) Collector. |
| -XX:+UseStringDeduplication |
String reduplication reduces the memory footprint of String objects on the Java heap. Instead of each String object pointing to its own character array, identical String objects can point to and share the same character array. This option is available from Java 8 update 20 going forward. (G1 specific setting) |
| -XX:+ParallelRefProcEnabled |
Determines whether processing of java.lang.Ref.* instances muxt be done in parallel by multiple threads. Enabling this setting reduces the time taken for processing reference objects. (G1 specific setting) |
| -XX:InitialHeapSize=1g | Sets the initial heap size. |
| -XX:MaxHeapSize=3g |
Sets the maximum heap size. This must be increased if the JVM's heap commit size approaches this limit. The G1 garbage collector is more efficient when sufficient heap space is available. |