JDK-8247843 : Reconsider G1 default GCTimeRatio value
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 16
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2020-06-18
  • Updated: 2021-07-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.
Other
tbdUnresolved
Related Reports
Blocks :  
JDK-8238687 - Investigate memory uncommit during young collections in G1
Description
In JDK-8238687 G1 will make committed heap more or less follow the GCTimeRatio. Which means that there may be throughput regressions due to keeping a smaller heap now.

Further in the last few years, pauses have been optimized a lot, now taking significantly less time.

So it is natural to think about rebalancing the GCTimeRatio default value decision made years ago.
Comments
Liang Mao from Alibaba mentioned that "for online interactive applications" something like 20 would be used in their setups. E.g. https://mail.openjdk.java.net/pipermail/hotspot-gc-dev/2020-June/030132.html
18-06-2020