Compatibility with generational ZGC #1006
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.
Non-generational Shenandoah and ZGC have two memory managers, one concurrent, one stop-the-world, named
<gc> Cycles
and<gc> Pauses
:However generational ZGC splits these into major/minor cycles/pauses:
Looks like there's no change required for genshen so far, they're using the same memory managers:
Allocation Stall
is also not a special case, and just another concurrent cycle trigger. It does indicate a allocation stall occurred, but it's not a pause and doesn't tell you how long threads were paused for:Found while testing genzgc early access builds: