Do not look at JIT startup state for turning GCR on/off #19863
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the JVM is in JITServer client mode, GCR counting will be enabled even during JIT startup phases (but not during JVM startup phase which only happens once). This allows GCR recompilations to happen sooner, improving rampup. In client mode there is a lesser risk that GCR recompilation overhead will impact the throughput of the JVM.
This change can be overridden by using the following environment variable:
export TR_LookAtJitStateForGCREnablement=1