JEP 173: Remove Rarely-Used Combinations of Garbage Collectors

lordpixel at me.com lordpixel at me.com
Tue Dec 18 20:01:13 PST 2012


On Dec 18, 2012, at 11:45 AM, Jon Masamitsu <jon.masamitsu at oracle.com> wrote:

>> Out of curiosity, is shrinking really a simple choice? Presumably leaving the heap larger means fewer collections and better performance overall if lots more garbage is created.
> 
> Hmmm.  Not sure I understand this question.
> Using an implementation that allows shrinking
> is a simple choice.  How it shrinks is more.


Yes, sorry, that wasn't very clear. What I meant was is it a simple choice when to shrink the heap vs. when to leave it large and empty after a full collection.

I talked a little about the reasons why I am thinking about this back in Feb, but this thread has gone off topic so I'll drop this unless you want more details about what I was trying to solve for.

AndyT (lordpixel - the cat who walks through walls)
A little bigger on the inside

	(see you later space cowboy, you can't take the sky from me)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20121218/5e7a7429/attachment.html 


More information about the hotspot-gc-dev mailing list