JDK-8059758 : Footprint regressions with JDK-8038423
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8u40,9
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-10-06
- Updated: 2017-07-26
- Resolved: 2014-10-09
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 | JDK 9 |
|---|---|
8u40Fixed  |
9 b37Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Recent changes in JDK-8038423 allow G1 to decommit regions within the heap freely, the VM always initializes associated auxiliary data structures (BOT, card table, mark bitmaps). This works somewhat against OSes lazy initialization of committed pages where they are actually only backed by physical memory on the first access. These startup benchmarks never actually use this memory because they are so simple, so this causes a footprint regression with the mentioned change.
Comments
|