-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b10
However, at each mixed-gc, depending on the G1MixedGCCountTarget, certain regions have to be collected together. With this in mind, we may have these regions share a single instance of G1CardSet. This can decrease the number of inter-remembered set pointers significantly for regions that will be collected at the same time.
The expected benefit is reduction in the memory overhead of the remembered set and the remembered set merge time during collection pause.
The one disadvantage is that this decreases the flexibility during evacuation slightly: you can only evacuate all regions that share a particular G1CardSet at once.
- causes
-
JDK-8349688 G1: Wrong initial optional region index when selecting candidates from retained regions
-
- Resolved
-
- duplicates
-
JDK-8058803 Allow one remembered set to be used for multiple regions
-
- Closed
-
- relates to
-
JDK-8351403 G1: Spiky pause times due to too large initial group selection
-
- Open
-
-
JDK-8349783 g1RemSetSummary.cpp:344:68: runtime error: member call on null pointer of type 'struct G1HeapRegion'
-
- Resolved
-
-
JDK-8349850 G1: Improve group selection based on expected time to evacuate
-
- Open
-
-
JDK-8336086 G1: Use one G1CardSet instance for all young regions
-
- Resolved
-
-
JDK-8058803 Allow one remembered set to be used for multiple regions
-
- Closed
-
- links to
-
Commit(master) openjdk/jdk/86cec4ea
-
Review(master) openjdk/jdk/22015