Request for review (S): 8003820: Deprecate untested and rarely used GC combinations

[Srinivas Ramakrishna]

Also, to a point that Peter Kessler made earlier. What is the performance
hit when you run ParNew with #gc threads = 1,
versus DefNew (with CMS in old gen of course) ? It would be good to measure
and know, even if we are ready to swallow
that hit for practical reasons.

-- ramki

On Wed, Dec 19, 2012 at 4:59 PM, Srinivas Ramakrishna <ysr1729 at gmail.com>wrote:

> Hi Bengt --
>
> Looks fine (although -- and this not part of the CR -- Arguments::parse()
> seems to have grown rather large and wants to
> be refactored into a few distinct pieces -- perhaps by "functional
> module"; but that's another bug).
>
> What happens when you run CMS on a single-processor. I hope you don't see
> a deprecation warning.
>
> -- ramki
>
>
>
> On Tue, Dec 18, 2012 at 6:02 AM, Bengt Rutisson <bengt.rutisson at oracle.com
> > wrote:
>
>>
>> Hi all,
>>
>> Can I have a couple of reviews for this change to deprecate the DefNew +
>> CMS and ParNew + SerialOld GC combinations?
>>
>> http://cr.openjdk.java.net/~brutisso/8003820/webrev.00/
>>
>>
>> This is part of the work for JEP 173:
>>
>> JEP 173: Retire Some Rarely-Used GC Combinations
>> http://openjdk.java.net/jeps/173
>>
>> The work is tracked in this bug:
>>
>> 8003820 : Deprecate untested and rarely used GC combinations
>> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8003820
>>
>> Thanks,
>> Bengt
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20121220/3741855d/attachment.htm>