-
Bug
-
Resolution: Fixed
-
P3
-
25
-
b16
When pruning the collection set before rebuild, only freed space is taken into account when selecting these regions (i.e. gc-efficiency).
This can cause G1 selecting extremely bad to evacuate regions (with low efficiency), which in turn then can cause pause time spikes, particularly in combination with grouping.
One option is to improve the gc efficiency calculation by using more information, like number of incoming references calculated during marking, so improve the selection.
Another option is to select more regions to build the remembered sets for and prune later again.
This can cause G1 selecting extremely bad to evacuate regions (with low efficiency), which in turn then can cause pause time spikes, particularly in combination with grouping.
One option is to improve the gc efficiency calculation by using more information, like number of incoming references calculated during marking, so improve the selection.
Another option is to select more regions to build the remembered sets for and prune later again.
- relates to
-
JDK-8262185 G1: Prune collection set candidates early
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/6879c446
-
Review(master) openjdk/jdk/24076