-
Enhancement
-
Resolution: Fixed
-
P3
-
hs17
-
b11
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2190659 | 7 | Tony Printezis | P3 | Closed | Fixed | b87 |
JDK-2197968 | 6u23 | Tony Printezis | P3 | Resolved | Fixed | b01 |
JDK-2199916 | 6u22m | Tony Printezis | P3 | Resolved | Fixed | b01 |
JDK-2193609 | 6u21p | Tony Printezis | P3 | Resolved | Fixed | b03 |
JDK-2189809 | 6u21 | Tony Printezis | P3 | Resolved | Fixed | b01 |
JDK-2190660 | hs18 | Tony Printezis | P3 | Closed | Fixed | b01 |
Currently, G1 will auto-tune the young generation size if the G1YoungGenSize parameter is not set. If G1YoungGenSize is set, G1 will use that as the young gen size.
To be consistent with the other GCs, G1 should observe UseAdaptiveSizePolicy to decide whether to auto-tune the young generation size. NewSize / MaxNewSize (and also -Xmn) should dictate the initial max size.
- backported by
-
JDK-2189809 G1: use existing command line parameters to set the young generation size
-
- Resolved
-
-
JDK-2193609 G1: use existing command line parameters to set the young generation size
-
- Resolved
-
-
JDK-2197968 G1: use existing command line parameters to set the young generation size
-
- Resolved
-
-
JDK-2199916 G1: use existing command line parameters to set the young generation size
-
- Resolved
-
-
JDK-2190659 G1: use existing command line parameters to set the young generation size
-
- Closed
-
-
JDK-2190660 G1: use existing command line parameters to set the young generation size
-
- Closed
-
- relates to
-
JDK-6928059 G1: command line parameter renaming
-
- Closed
-
-
JDK-6929868 G1: introduce min / max young gen size bounds
-
- Closed
-