JDK-8245088 : Always provide logs for G1 heap expansion calculations
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-05-15
- Updated: 2024-09-28
- Resolved: 2020-05-26
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 15 |
|---|
15 b25Fixed  |
Related Reports
|
Blocks :
|
|
|
Blocks :
|
|
|
Blocks :
|
Description
Currently we only log heap expansion calculations (inputs/outputs) when we actually perform changes to the heap expansions. However heap expansion is based on long term application behavior, so the result is often not sufficient to explain that result easily. Always, at every gc, provide information about the current state.
Comments
|