Hi Charlie,
An excellent summary. I like Mark’s suggestion that there be a path to roll back should we discover something before GA.
Regards,
Kirk
BTW, I’ve reconfigured everything I use to use G1
On Jun 5, 2015, at 12:08 AM, mark.reinhold at oracle.com wrote:
> 2015/6/4 6:44 -0700, charlie.hunt at oracle.com:
>> Wanted to come back to this thread, continue the dialog, reiterate the
>> objective, (try to) summarize the concerns and put forth a potential
>> plan for this JEP going forward.
>>>> Intent: Use G1 GC as the default collector chosen by the JVM when no
>> GC is explicitly set at the JVM command line.
>>>> ...
>> Charlie -- thanks for the excellent summary of this wide-ranging
> discussion!
>>> ...
>>>> Suggested plan for moving forward:
>> - Make G1 the default collector in JDK 9, continue to evaluate G1 and
>> enhance G1 in JDK 9
>> - Mitigate risk by reverting back to Parallel GC before JDK 9 goes
>> “Generally Available” (Sept 22, 2016 [1]) if warranted by continuing
>> to monitor observations and experiences with G1 in both JDK 9
>> pre-releases and latest JDK 8 update releases
>> - Address enhancing ergonomics for selecting a default GC as a
>> separate JEP if future observations suggests its needed
>> I think this is a fine plan.
>> Stefan -- To move forward with JEP 248, could you please revise the
> second item in the "Risks and Assumptions" section to note that there
> is some concern that G1 might not be ready to become the default, that
> making it the default now will allow us to get more feedback on it, and
> that if it proves to be not ready then we'll revert the default to the
> Parallel GC in time for JDK 9 GA?
>> Ben -- Can you live with this plan?
>> - Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20150605/fd64b157/signature.asc>