JDK-8033426 : Scale initial NewSize using NewRatio if not set on command line
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-02-03
  • Updated: 2014-07-29
  • Resolved: 2014-02-13
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.
8u20Fixed 9 b04Fixed
Right now the initial NewSize is the same as the minimal NewSize if not set on the command line. For a large heap this is not optimal. NewRatio is currently used for sizing Old vs New for the maximum sizes, it should also be used for initial sizes.
We want this enhancement to be backported to 8u20 to get rid of the regression in 8 where the default young generation size is always 1.5M. Doing an ILW to get proper prio. ILW => MHL => P3 Impact: Medium, unexpectedly low young generation size. Will cause early GCs. Likelihood: High, always with default settings. Workaround: Low, set NewSize.