-
Enhancement
-
Resolution: Fixed
-
P4
-
16
-
b14
At the end of gc we need to iterate over all regions where evacuation failed to fix up self-forwarded pointers.
Currently, particularly afterJDK-8254164, we iterate over all collection set regions in parallel with all threads.
This is a problem with current work distribution: since we do not know how many regions with actual work there are, we spin up all available threads, with no idea
- which thread gets to do which region.
- how much work is actually there, causing issues with synchronization of spinning up and down lots of threads unnecessarily
Currently, particularly after
This is a problem with current work distribution: since we do not know how many regions with actual work there are, we spin up all available threads, with no idea
- which thread gets to do which region.
- how much work is actually there, causing issues with synchronization of spinning up and down lots of threads unnecessarily
- relates to
-
JDK-8273192 G1: Improve thread sizing for evacuation failure
- Open
-
JDK-8256265 G1: Improve parallelism in regions that failed evacuation
- Resolved
-
JDK-8273476 G1: refine G1CollectedHeap::par_iterate_regions_array_part_from
- Resolved
-
JDK-8279856 Parallel: Use PreservedMarks to record promotion-failed objects
- Resolved
-
JDK-8273492 Move evacuation failure handling into G1YoungCollector
- Resolved
-
JDK-8236594 G1: Provide object pinning
- Closed
-
JDK-8276094 JEP 423: Region Pinning for G1
- Closed
(2 relates to, 2 links to)