JEP 173: Remove Rarely-Used Combinations of Garbage Collectors
ysr1729 at gmail.com
Thu Dec 6 12:55:41 PST 2012
+1 to all those observations.
Don't know how it affects sharing of code wrt "embedded" and other smaller
footprint jvm's, if any, though....
I am sure that has been thought through at the right places, but good to
keep in mind.
On Wed, Dec 5, 2012 at 4:23 PM, Peter B. Kessler <Peter.B.Kessler at oracle.com
> mark.reinhold at oracle.com wrote:
>> Posted: http://openjdk.java.net/jeps/**173<http://openjdk.java.net/jeps/173>
>> - Mark
> If the only use of SerialOld will be with ParallelScavenge + SerialOld,
> then maybe we should check what the performance hit (GC time, heap
> utilization, application throughput) is using ParallelScavenge +
> ParallelOld, possibly with ParallelOld throttled down to 1 worker thread.
> (I understand that we can't remove the code for SerialOld because it backs
> CMS, but we could improve the user experience by not letting people choose
> sub-optimal configurations.) Similarly, if we could start weaning users
> off of DefNew we might eventually be able to remove the code for it.
> It would help the write-up if the *supported* configurations were listed.
> ... peter
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev