JVM Tuning

Below is the list of recommended JVM options for high performance GridGain installations in embedded mode:

Do not set the maximum heap size (-Xmx) to a value between 32 GB and roughly 47 GB. A heap in that range holds less data than a 31 GB heap does.

Below 32 GB, the JVM stores object references as 32-bit values, a technique called compressed ordinary object pointers, or compressed oops. At 32 GB the JVM turns compressed oops off, every reference grows from 4 to 8 bytes, and every object that holds references grows with them, so fewer objects fit. The heap has to reach roughly 47 GB before the added capacity makes up for the larger references. The exact crossover depends on how many references your data holds.

Set -Xmx to 31 GB or less, or to well above 47 GB. Raising a 31 GB heap to 40 GB can cause the very OutOfMemoryError it was meant to prevent.

G1 is a recommended collector for GridGain.

Normally G1 collector doesn’t require any special tuning due to its adaptive behavior and works fine out of the box.

However, you can try other collectors, like ZGC and see if they work better for you workload. Collectors availability depends on JVM vendor.

All worker pools are sized automatically and don’t require special tuning.

G1 garbage collector is NUMA-aware since release 14. It can be enabled with: