JDK-8241670 : Enhance heap region size ergonomics to improve OOTB performance
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 11,15
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-03-26
- Updated: 2021-02-04
- Resolved: 2020-04-02
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 b18Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Sub Tasks
|
JDK-8242057 :
|
Description
The way we currently choose the heap region size in G1 can sometimes give worse OOTB performance than expected. In recent benchmarking the difference between setting a fixed heap size of 4g and letting it get a default max heap of 4g was bigger than expected. Running SPECjbb2015, the max-jOPS increased with ~40% and critical-jOPS increased 130% when setting a fixed heap size. The main reason behind the improvement is that when running with a fixed heap size the region size will be 2m instead of 1m. This difference comes from the fact that both the initial and max heap size is considered when calculating the heap region size ergonomically. We should look into changing this to give a better out of the box behavior.
Comments
|