JDK-6814390 : G1: remove the concept of non-generational G1
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs15
- Priority: P5
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2009-03-06
- Updated: 2013-09-18
- Resolved: 2011-09-30
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 | JDK 8 | Other |
|---|---|---|
7u2Fixed  |
8Fixed |
hs22Fixed |
Description
Right now, the G1 code can be run (at least in theory!) in two modes: generational and non-generational. We use and test the generational mode which has major performance benefits over the non-generational mode and, as a result, the non-generational mode is probably bit rotted. We should just get rid of the non-generational mode to simplify the G1 code.
Comments
|