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 Jira’s performance.

This code cache is primarily controlled by the ReservedCodeCacheSize property. Starting from Jira 7.13, this property is set to 512 MB by default in the setenv.sh / .bat file. If you have a large Jira instance, you may still 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
Pass	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.
Warning	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 with Jira.
Warning	Your JVM code cache memory is below the recommended limit.	We recommend increasing the maximum size of the code cache to avoid performance issues with Jira.
Fail – critical	Your JVM doesn’t have enough free space allocated to code caching. This could be causing performance issues with Jira.	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 ReservedCodeCacheSize limit to avoid performance issues with Jira.

Resolution

If you’ve reached the limit of the code cache, we recommend increasing the ReservedCodeCacheSize property to 512 MB.

To do this, add the following arguments to the Java startup options by following the instructions in Setting Properties and Options on Startup:

-XX:ReservedCodeCacheSize=512m

Restart Jira for the new settings to take effect.