Health Check: JVM Code Cache
Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.
About the health check
This check verifies that you’re using the recommended JVM (Java Virtual Machine) configuration for code cache memory.
The JVM generates native code and stores it in a memory area called the Code cache.
Insufficient code cache memory can cause the JVM to disable its just-in-time (JIT) compilers, which can have a significant impact on Confluence’s performance.
This code cache is primarily controlled by the
ReservedCodeCacheSize property. This property is set to 256 MB by default in the setenv.sh / .bat file. If you have a large Confluence instance, you may need to increase the size.
This health check is only shown if you use Java 1.8 or above.
Understanding the results
|Icon||Result||What it means|
Your JVM has enough memory available for the code cache and compilers to run properly.
You're using the recommended configuration. There's currently sufficient memory available for the JVM’s code cache and C1/C2 compilers to run correctly.
Your JVM is approaching the limit of memory allocated to code caching.
We recommend increasing the maximum size of the code cache to avoid performance issues.
Your JVM code cache memory is below the recommended limit.
|We recommend increasing the maximum size of the code cache to avoid performance issues.|
|Your JVM doesn’t have enough free space allocated to code caching. This could be causing performance issues.|
The JVM’s code cache has breached its limits and the JVM is very likely to have disabled its C1/C2 compilers.
We recommend increasing the
If you’ve reached the limit of the code cache, we recommend increasing the
ReservedCodeCacheSize property to 384 MB.
To do this, add the following arguments to the Java startup options by following the instructions in Configuring System Properties
Restart Confluence for the new settings to take effect.