JDK-8267836 : Separate eager reclaim remembered set threshold from G1RSetSparseRegionEntries
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-05-27
- Updated: 2021-06-07
- Resolved: 2021-06-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 17 |
|---|
17 b25Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Currently the remembered set eager reclaim threshold is based on G1RSetSparseRegionEntries. I.e. otherwise eligible humongous objects are only considered candidates for eager reclaim if their remembered set has less than G1RSetSparseRegionEntries entries. The reason for this limitation has been that before JDK-8233919 (in JDK14) it has been very expensive to get a remembered set size estimate if the remembered set for that heap region had expanded to fine tables. This is not the case any more, and there are situation where you want to set this threshold (much) larger than the number of sparse table entries. By default, this new value should still be based on the current value.
Comments
|