JDK-7029458 : G1: Add newly-reclaimed regions to the beginning of the region free list, not the end
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs21
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-03-21
- Updated: 2013-09-18
- Resolved: 2011-04-24
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 7 | Other |
|---|---|
7Fixed  |
hs21Fixed |
Description
Currently, when we reclaim one or more regions we always add them to the end of the free list. Based on testing our performance team did, this seems to be pathological for applications that grow the heap very slowly given that regions that have just been reclaimed will be the last to be re-allocated, which causes us to "churn" unnecessarily through the free regions and touching the entire address space of the G1 heap even though we don't have to.
Comments
|