JDK-6864886 : G1: rename -XX parameters related to update buffers
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs16
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-07-24
  • Updated: 2013-09-18
  • Resolved: 2009-08-22
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 6 JDK 7 Other
6u18Fixed 7Fixed hs16Fixed
From an e-mail I recently sent:

I noticed that some G1 parameters are very badly (and inconsistently) named!

In g1_globals.hpp:

1) G1DirtyCardQueueMax - maximum update buffer queue length before mutators start processing update buffers

In globals.hpp:

2) DCQBarrierQueueBufferSize - length (it's not really size) of the update buffers
3) DCQBarrierProcessCompletedThreshold - how many update buffers must be in the queue before concurrent refinement threads start processing them

First, given that 2) and 3) are only used by G1, I think they should get the G1 prefix (and be moved to the g1_globals.hpp file). Second, I'd like to make the parameter names more consistent. These are the proposed new names:

1) G1UpdateBufferQueueMaxLength
2) G1UpdateBufferLength
3) G1UpdateBufferQueueProcessingThreshold

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/27f6a9b9c311

EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/27f6a9b9c311

EVALUATION See Description.