JDK-8003822 : Deprecate the incremental mode of CMS
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs25
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- CPU: other
- Submitted: 2012-11-21
- Updated: 2017-05-17
- Resolved: 2013-01-04
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 8 | Other |
|---|---|
8Fixed  |
hs25Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
The incremental mode of CMS (i-CMS) was introduced when the train collector was removed in 2005/2006. This is a mode that targets single (or maybe dual) CPU machines. i-CMS is not used much and has been kind of made obsolete by the current trend towards multi core platforms. The i-CMS code is expensive to maintain and add to the complexity in the GC code. We are currently testing i-CMS, but there are more important GC combinations to test. So, i-CMS uses up test resources that we could use for more widely used GC combinations. To simplify the GC code and enable testing of all GC combinations that we support we should remove i-CMS. We can only remove a GC in an major release, so the plan is to remove it for the upcoming JDK8 release.
Comments
|