JDK-8153507 : Improve Card Table Clear Task
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-04-05
  • Updated: 2017-04-12
  • Resolved: 2016-05-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b120Fixed
Related Reports
Blocks :  
Blocks :  
Duplicate :  
Relates :  
Description
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.