JDK-8233919 : Incrementally calculate the occupied cards in a heap region remembered set
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 14
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-11-11
- Updated: 2021-05-27
- Resolved: 2019-12-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.
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 14 |
|---|
14 b26Fixed  |
Related Reports
|
Blocks :
|
|
|
Blocks :
|
|
|
Blocks :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Currently a remembered set's occupancy is calculated from its components. This is problematic for a few reasons: - slow on remembered sets with lots of components, which causes lots of additional code to avoid recalculation or mitigations - may cause the total count going down temporarily when calculating during coarsening; attempting to account for this adds additional code Particularly for updating predictions at mutator time such a temporary wrong value may cause unexpected prediction results.
Comments
|