JDK-8237261 : Concurrent refinement activation threshold not updated for card counts
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 14,15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-01-16
- Updated: 2020-01-23
- Resolved: 2020-01-20
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 15 |
|---|
15 b07Fixed  |
Related Reports
|
Relates :
|
Description
JDK-8230109 changed G1 concurrent refinement to track the number of enqueued cards rather than the number of buffers, and to compute the activation and deactivation thresholds for the threads in units of cards rather than buffers. However, the activation threshold for the primary refinement thread is handled specially, potentially being activated more aggressively than the normal calculation would suggest. That special case was not updated for the change from units of buffers to units of cards. As a result, the primary thread will likely be activated much more aggressively than intended.
Comments
|