JDK-8246274 : G1 old gen allocation tracking is not in a separate class
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 11,14,15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2020-06-01
- Updated: 2024-10-17
- Resolved: 2020-06-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 11 | JDK 15 |
|---|---|
| 11.0.12Fixed | 15 b27Fixed  |
Related Reports
|
Blocks :
|
Description
To better shape fixing JDK-8245511, this was suggested in its comments: "- one other improvement could be to put the old gen allocation tracking into its own class (e.g. G1OldGenAllocationTracker; which G1Policy has an instance of) to not add too much detail to the IHOP code itself. In G1IHOPControl::update_allocation_info() then pass the expected allocation rate as experienced by/relevant to the IHOP control as it is in now its respective components. " In general, the enhancement proposal is to track old gen allocations in a separate class so that this concern can be worked upon in a more clearly/cleanly delineated source code context. After implementing this refactoring cleanly, without any change in behavior, other improvements can follow.
Comments
|