-
Enhancement
-
Resolution: Won't Fix
-
P3
-
9
Clearing the per-thread concurrent mark data structures is single threaded. This is a bad idea in case of large heaps, significantly lengthening the concurrent mark cycle.
Parallelize this phase.
Parallelize this phase.
- duplicates
-
JDK-8067500 ConcurrentMark::abort() is excessively slow
- Closed
- relates to
-
JDK-8151125 Unify clearing mark bitmaps and concurrent mark data structures
- Closed
-
JDK-8077144 Concurrent mark initialization takes too long
- Closed