-
Enhancement
-
Resolution: Fixed
-
P4
-
21
-
b23
The current implementation is not well suited for this:
* currently collection set candidate handling is fairly ad-hoc, e.g. not having explicit sets that can e.g. be iterated over directly. This is especially bad since for
* current collection set candidates are only materialized when there are candidates from end of marking to end of the mixed gc phase. Evacuation failure/region pinning may occur any time, so we need to keep around the candidate list(s) all the time.
* this is a good opportunity to move the _gc_efficiency member out from HeapRegion as it's only needed for the candidates
- relates to
-
JDK-8140326 G1: Consider putting regions where evacuation failed into next collection set
-
- Resolved
-