JVM Thread and Memory Parameter Tuning Recommendations for Containerized Environments

The JVM startup parameters related to threads and memory can cause high CPU usage and frequent GC in production, especially on older JDK versions that cannot detect Docker resource limits.

1. Thread Parameters

ParallelGCThreads controls the number of GC threads during parallel collection. A larger value reduces pause time but may lower throughput. The default is calculated as:

if ncpus < 8: ParallelGCThreads = ncpus

else: ParallelGCThreads = 8 + (ncpus - 8) * 5/8

Experiments with an 8C/12G container showed that setting ParallelGCThreads to 8 reduces CPU usage by about 5% under steady load and allows faster recovery when the CPU spikes.

Recommended actions:

Upgrade JDK to 1.8.0_131 or later (preferably 1.8.0_191+).

Explicitly set -XX:ParallelGCThreads=[n] according to the table below:

Container CPUs

2

4

8

16

32

64

Recommended value

2

4

8

13

23

43

Suggested range

1‑2

2‑4

4‑8

8‑16

16‑32

32‑64

Other important thread parameters include ConcGCThreads (concurrent GC threads) and CICompilerCount (JIT compilation threads). For JDK 8 before 1.8.0_131, their defaults can be excessively high; they should be set explicitly when needed, e.g., -XX:ConcGCThreads=2 and -XX:CICompilerCount=2.

2. Memory Parameters

Heap (On‑heap) Memory is controlled by -Xms, -Xmx, -XX:NewRatio, etc. Recommended defaults for containers are:

If container memory ≤ 2 GB: Xmx = 50% of container memory (min 16 MB, max 512 MB).

If container memory > 2 GB: Xmx = 25% of container memory (max 32 GB).

Xms defaults to 1/64 of container memory (min 8 MB) unless Xmx is smaller.

Set Xms equal to Xmx in production to avoid heap size fluctuations.

Off‑heap Memory includes Direct Byte Buffers and Metaspace. Direct Byte Buffers improve I/O performance but can leak if not released; set -XX:MaxDirectMemorySize and ensure -XX:+DisableExplicitGC is not disabling GC of these buffers.

Metaspace replaces PermGen in JDK 8. Specify -XX:MaxMetaspaceSize and -XX:MetaspaceSize (often set to the same value) to avoid unbounded growth.

Example startup options (replace bracketed values with the recommended numbers):

-server -Xms8192m -Xmx8192m -XX:MaxDirectMemorySize=4096m -XX:ParallelGCThreads=8 -XX:ConcGCThreads=2 -XX:CICompilerCount=2 -XX:MaxMetaspaceSize=256m -XX:MetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/export/Logs

Finally, enable OOM heap dumps with -XX:+HeapDumpOnOutOfMemoryError and set -XX:HeapDumpPath to a suitable location.

These recommendations should be validated with load testing and monitoring to ensure they suit the specific workload.