JDK-6929868 : G1: introduce min / max young gen size bounds
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs18,hs21
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-02-25
  • Updated: 2013-10-04
  • Resolved: 2011-11-28
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.
JDK 7 JDK 8 Other
7u2Fixed 8Fixed hs22Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
Right now, when the young gen size auto-tuning in G1 is enabled (with UseAdaptiveSizePolicy), G1 sets the young gen size to what the ergonomic code calculates and does not obey and min / max bounds (even if NewSize / MaxNewSize have been explicitly set).

We should introduce min / max young gen size limits. The defaults of those limits should be very aggressive (e.g., maybe 1-2 regions for min, 50% of the heap for max). Those limits should be also settable by the user with NewSize / MaxNewSize.

Comments
EVALUATION See main CR
12-09-2011

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-gc/hotspot/rev/af2ab04e0038
08-09-2011