JDK-8196071 : Change G1 Full GC heap and thread sizing ergonomics
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 11
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-01-24
- Updated: 2018-04-26
- Resolved: 2018-04-19
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 |
|---|
11 b11Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The heap sizing after the new Full GC differs a bit from the old one, since we now use many threads we will almost always use more than one region after the Full GC is done. This will in turn lead to a more restrictive shrinking of the heap, leaving more regions around after a System.gc() than before. This can improved by not using as many threads when the heap is small, and one way to scale the number of threads is to use the G1HeapWastePercent value to make sure we don't end up with too many "wasted" regions which in turn will affect the total heap size.