- Best Practice For Java Memory Heap settings
- CloudBees CI (CloudBees Core) on Modern Platforms
- CloudBees CI (CloudBees Core) on Traditional Platforms
- CloudBees Jenkins Distribution
- CloudBees Jenkins Team (CJT)
- CloudBees Jenkins Platform - Client controller (CJP-CM)
- CloudBees Jenkins Platform - Operations Center (CJP-OC)
- CloudBees Jenkins Enterprise (CJE)
- Jenkins LTS
In a traditional platform, where Jenkins runs on the system directly, the java arguments
Xms can be used to set respectively the maximum and the initial JVM memory heap sizes.
In a modern platform or when running Jenkins in a container, those settings are deprecated. Since JDK 8u191
XX:+UseContainerSupport is activated by default, the JVM is “container-aware” and can determine its heap size based on the container boundaries. It also introduces
-XX:InitialRAMPercentage which takes a value between 0 and 100 (Note: values should be double type see docker-library/openjdk/issues/350). This allows fine-grained control of the amount of RAM the JVM is allowed to allocate.
Recommended Heap Specifications can be found in CloudBees JVM Guide.
Ensure container memory
requests are equal and use
For Jenkins instances, it is recommended to use a Guaranteed QoS (same request and limits) to avoid impact with other containers and unexpected evictions and restarts caused by node memory pressures.
... resources: limits: memory: 6Gi requests: memory: 6Gi ...
Defining just the
limits assumes the same
... resources: limits: memory: 6Gi ...
-XX:InitialRAMPercentage=50.0 -XX:MaxRAMPercentage=50.0 Java arguments as per How to add Java arguments to Jenkins.
a. Do not enable
Enable heap ratio because it calculates the JVM Heap size from the
Jenkins Controller Memory in MB and injects
-Xms to the controllers JVM (which is not recommended).
b. Do not set
-Xms. Those options set the JVM Heap size directly and it is best to let the JVM infer these based on current
-XX:InitialRAMPercentage instead. If
-Xmx is passed, the JVM will ignore
-XX:MaxRAMPercentage (respectively, if
-Xms is passed, the JVM will ignore
c. Do not use a ratio JVM heap / Container Memory limit higher than
0.5. It is known to be unstable and may cause unexpected controller restarts due to JVM off heap usage. Note that the JVM default to use a ratio of
d. Do not set
-XX:MinRAMPercentage. It is used to compute Java heap size only if your overall available memory’s size in the physical server (or in the container) is less than 250MB (approximately). A Host with 250 MB of memory would not been able to support the minimal requirement of Heap Size for CloudBees CI on Production Enviroments: 4GB (See CloudBees Jenkins JVM troubleshooting - Heap Size).
e. Do not set
-XX:MaxRAMFraction. It is deprecated in favor of
MaxRAMPercentage see JDK-8186315 and After upgrading CloudBees CI on modern platform, the Operation Center - Controller is getting restarted often.
For a more detailed explanation on the meaning of
MaxRAMPercentage, refer to Differences between InitialRAMPercentage, MinRAMPercentage, MaxRAMPercentage.
Use your favorite APM tool to monitor the Memory Heap Consumption by your instance. The right heap value should be a value between 80-90% of total heap consumption when the instance is at the maximum workload. Increased heap memory will produce long Garbage Collection pauses, which can be observed via slowness in the UI and sometimes even side effects like agent disconnections.
If your instance is not able to support its current workload (due to number of jobs and dynamic configurations) you should consider scaling horizontally your infrastructure by adding more controllers to divide the workload more efficiently.