Avoiding the Young Generation Guarantee

Alex Aisinzon aaisinzon at guidewire.com
Mon Mar 10 19:34:14 UTC 2008



I thank you for your feedback.

I use the ParNewGC, which according to Jon's blog
<http://blogs.sun.com/jonthecollector/> ) is the combination of "ParNew"
+ "Serial Old".

Therefore, I do not use the UseConcMarkSweepGC.

I am using JDK 1.5.0_14.


I would not expect the young generation to be applied. The logs seem to
indicate that it is.


Alex A



From: Jones, Doug H [mailto:doug.jones at eds.com] 
Sent: Monday, March 10, 2008 12:15 PM
To: Alex Aisinzon
Subject: RE: Avoiding the Young Generation Guarantee


Hi Alex,


It is not supposed to be the case under JVM version 5.0 on, it
definitely was under JVM 1.4.2. I'm assuming you are using
ConcMarkSweepGC of the tenured area.





	From: hotspot-gc-use-bounces at openjdk.java.net
[mailto:hotspot-gc-use-bounces at openjdk.java.net] On Behalf Of Alex
	Sent: Tuesday, 11 March 2008 7:50 a.m.
	To: hotspot-gc-use at openjdk.java.net
	Subject: Avoiding the Young Generation Guarantee



	Our application scales very well when more memory is allocated
to it.

	The Young Generation Guarantee limits that scalability as it
forces Full GC while plenty of space is still available in the tenured

	That guarantee forces us to use relatively smaller nurseries.

%20Generation%20Guarantee%7Coutline infers that this guarantee only
applies to the serial collector but I see it too with the parallel new

	Maybe I am confused in the collector terminology.

	Could someone tell me how I can disable the young generation


	Thanks in advance


	Alex A


	I have enclosed a snippet of the GC logs for analysis purposes.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/hotspot-gc-dev/attachments/20080310/946961ad/attachment.htm>
-------------- next part --------------
hotspot-gc-use mailing list
hotspot-gc-use at openjdk.java.net

More information about the hotspot-gc-dev mailing list