JDK-8001425 : G1: Change the default values for certain G1 specific flags
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs25
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2012-10-23
  • Updated: 2013-09-18
  • Resolved: 2013-01-16
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
7u21Fixed 8Fixed hs24Fixed
Related Reports
Duplicate :  
JDK-8001421 - Backport (and name change) certain important command line flags for G1
Relates :  
JDK-8001424 - G1: Rename certain G1-specific flags
Description
When testing footprint sensitive FAs; the performance team has realized that the default values are not good enough. Hence we propose the following - 
Change the default for G1OldCSetRegionLiveThresholdPercent to 65
Change the default for G1HeapWastePercent to 10
Comments
I think its OK to go ahead with the broadened scope of default changes for Nursery min & max percent. I was just being conservative with my original defaults change request.
16-01-2013
After posting a webrev to the open jdk, the general feedback was why limit the revised values for NewSizePercent and MaxNewSizePercent to heaps under 4GB. There isn't any real reason not to extend these values to all heap sizes.
16-01-2013
Additional suggestions from the performance team: * Increase MixedGCCountTarget from 4 to 8. * For heaps that do not exceed 4Gb reduce the NewSizePercent to 5 and reduce the MaxNewSizePercent to 60.
06-12-2012