After remembered set scanning we need to clear the card table as remembered set scanning uses it to decrease overscan during remembered set scan. It and the related temporary data structures are located across several classes and methods. This makes it hard to modify it, and introduces unnecessary code for verification.
Further, the current way of doing this is very slow since it distributes work across threads using a single linked list of elements and a single claim value. In some cases we noticed that the Atomic claim of a new region is more expensive than the actual clearing of the corresponding bitmap.
Move card table clear handling to G1RemSetScanState to hide its implementation from the outside, and tune the thread usage.
Further, the current way of doing this is very slow since it distributes work across threads using a single linked list of elements and a single claim value. In some cases we noticed that the Atomic claim of a new region is more expensive than the actual clearing of the corresponding bitmap.
Move card table clear handling to G1RemSetScanState to hide its implementation from the outside, and tune the thread usage.
- duplicates
-
JDK-8150364 Clear CT phase work distribution too fine-grained
-
- Closed
-
- is blocked by
-
JDK-8153503 Move remset scan iteration claim to remset local data structure
-
- Resolved
-
-
JDK-8155232 Augment Workgang to run task with a given number of threads
-
- Resolved
-
- relates to
-
JDK-8017163 G1: Refactor remembered sets
-
- Resolved
-