|
Quick Lists
|
|
Bug ID:
|
6864886
|
|
Votes
|
0
|
|
Synopsis
|
G1: rename -XX parameters related to update buffers
|
|
Category
|
hotspot:garbage_collector
|
|
Reported Against
|
|
|
Release Fixed
|
hs16(b08),
6u18(b01) (Bug ID:2181932)
, 7(b71) (Bug ID:2182213)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
24-JUL-2009
|
|
Description
|
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
Posted Date : 2009-07-24 22:27:15.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
See Description.
Posted Date : 2009-07-24 22:42:34.0
http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/27f6a9b9c311
Posted Date : 2009-07-29 18:54:54.0
http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/27f6a9b9c311
Posted Date : 2009-07-31 20:10:12.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
