|Flag||What it does||When to use it||See also|
Chooses the server compiler
For long-running applications that need fast performance
Chooses the client compiler
For applications where start-up is the most important factor
Utilize tiered compilation (both client and server)
For applications where you want the best possible performance and have enough available native memory for the extra compiled code
Reserves space for code compiled by the JIT compiler
When you see a warning that you are out of code cache, and generally with when using tiered compilation.
Allocates the initial space for code compiled by the JIT compiler
If you need to pre-allocate the memory for the code cache, which is very uncommon.
The number of times a method or loop is executed before compiling it.
When using the server compiler, can cause more methods to be compiled, and methods to be compiled sooner. The first case is sometimes an advantage if you aren’t using tiered compilation.
Provide a log of operations by the JIT compiler.
When you suspect an important method isn’t being compiled, or are generally curious as to what the compiler is doing.