<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Drastically reducing GC pause times for YQL</title>
	<atom:link href="http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/</link>
	<description>Rants about Java and other internet technologies by Sam Pullara</description>
	<lastBuildDate>Mon, 08 Mar 2010 00:20:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: spullara</title>
		<link>http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/comment-page-1/#comment-1020</link>
		<dc:creator>spullara</dc:creator>
		<pubDate>Sun, 08 Nov 2009 00:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.javarants.com/?p=1241#comment-1020</guid>
		<description>Could it be the type of workloads you are throwing at it?  We&#039;ve had 30 VMs under load in production for the last week with great, low pause times without a hint of instability.  I&#039;ll take a crack at it with your options and see what we see.  G1 so far has been useless with full pauses being long and frequent under moderate testing.  Ran a 24 hour test last night of JRockit and their deterministic GC with excellent results for our workloads.  We also don&#039;t use Solaris. It is all RHEL.</description>
		<content:encoded><![CDATA[<p>Could it be the type of workloads you are throwing at it?  We&#39;ve had 30 VMs under load in production for the last week with great, low pause times without a hint of instability.  I&#39;ll take a crack at it with your options and see what we see.  G1 so far has been useless with full pauses being long and frequent under moderate testing.  Ran a 24 hour test last night of JRockit and their deterministic GC with excellent results for our workloads.  We also don&#39;t use Solaris. It is all RHEL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spullara</title>
		<link>http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/comment-page-1/#comment-998</link>
		<dc:creator>spullara</dc:creator>
		<pubDate>Sat, 07 Nov 2009 16:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.javarants.com/?p=1241#comment-998</guid>
		<description>Could it be the type of workloads you are throwing at it?  We&#039;ve had 30 VMs under load in production for the last week with great, low pause times without a hint of instability.  I&#039;ll take a crack at it with your options and see what we see.  G1 so far has been useless with full pauses being long and frequent under moderate testing.  Ran a 24 hour test last night of JRockit and their deterministic GC with excellent results for our workloads.  We also don&#039;t use Solaris. It is all RHEL.</description>
		<content:encoded><![CDATA[<p>Could it be the type of workloads you are throwing at it?  We&#39;ve had 30 VMs under load in production for the last week with great, low pause times without a hint of instability.  I&#39;ll take a crack at it with your options and see what we see.  G1 so far has been useless with full pauses being long and frequent under moderate testing.  Ran a 24 hour test last night of JRockit and their deterministic GC with excellent results for our workloads.  We also don&#39;t use Solaris. It is all RHEL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ari Zilka</title>
		<link>http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/comment-page-1/#comment-997</link>
		<dc:creator>Ari Zilka</dc:creator>
		<pubDate>Sat, 07 Nov 2009 02:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.javarants.com/?p=1241#comment-997</guid>
		<description>Uhm,  our work with the JVM shows Concurrent collector highly unstable and several folks in high places who shall remain nameless say never to use it.  Also, OS / platform is important.  On Solaris / CMT, run LargePageSizes and about as many ParallelGC threads as you have CMT threads (32, 64, or 128).  &lt;br&gt;&lt;br&gt;-XX:SurvivorRatio=8 – large survivor spaces for short-lived objects&lt;br&gt;-XX:+UseParallelGC&lt;br&gt;-XX:ParallelGCThreads=20&lt;br&gt;-XX:+UseParallelOldGC&lt;br&gt;-Xmn1g&lt;br&gt;-server switch&lt;br&gt;&lt;br&gt;Last, if you insist on CMS, then we have used ParNewGC + CMS and initiatingOccupancyFraction to get the GC to kick off aggressively and keep down the Full pauses.  &lt;br&gt;&lt;br&gt;G1 is going to have to dig us all out of the whole the CMS is burying us in, but Parallel w/ LOTS of threads has proved way more stable for us w/o the stop-the-worlds from CMS that can be like 3 hours...</description>
		<content:encoded><![CDATA[<p>Uhm,  our work with the JVM shows Concurrent collector highly unstable and several folks in high places who shall remain nameless say never to use it.  Also, OS / platform is important.  On Solaris / CMT, run LargePageSizes and about as many ParallelGC threads as you have CMT threads (32, 64, or 128).  </p>
<p>-XX:SurvivorRatio=8 – large survivor spaces for short-lived objects<br />-XX:+UseParallelGC<br />-XX:ParallelGCThreads=20<br />-XX:+UseParallelOldGC<br />-Xmn1g<br />-server switch</p>
<p>Last, if you insist on CMS, then we have used ParNewGC + CMS and initiatingOccupancyFraction to get the GC to kick off aggressively and keep down the Full pauses.  </p>
<p>G1 is going to have to dig us all out of the whole the CMS is burying us in, but Parallel w/ LOTS of threads has proved way more stable for us w/o the stop-the-worlds from CMS that can be like 3 hours&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spullara</title>
		<link>http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/comment-page-1/#comment-995</link>
		<dc:creator>spullara</dc:creator>
		<pubDate>Wed, 04 Nov 2009 13:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.javarants.com/?p=1241#comment-995</guid>
		<description>We are currently on java version 1.6.0_16.  We haven&#039;t yet seen a crash with this configuration.</description>
		<content:encoded><![CDATA[<p>We are currently on java version 1.6.0_16.  We haven&#39;t yet seen a crash with this configuration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amit Naik</title>
		<link>http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/comment-page-1/#comment-993</link>
		<dc:creator>Amit Naik</dc:creator>
		<pubDate>Wed, 04 Nov 2009 07:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.javarants.com/?p=1241#comment-993</guid>
		<description>Which specific version of 1.6 are you using? We have seen some GC related crashes with 1.6_06, 14,15 while using the CMS collector so we switched back to using the throughput collector. Did you happen to run into this?</description>
		<content:encoded><![CDATA[<p>Which specific version of 1.6 are you using? We have seen some GC related crashes with 1.6_06, 14,15 while using the CMS collector so we switched back to using the throughput collector. Did you happen to run into this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: h0h0h0</title>
		<link>http://www.javarants.com/2009/11/03/drastically-reducing-gc-pause-times-for-yql/comment-page-1/#comment-992</link>
		<dc:creator>h0h0h0</dc:creator>
		<pubDate>Wed, 04 Nov 2009 03:04:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.javarants.com/?p=1241#comment-992</guid>
		<description>Tight.  I love the black magic that you can get with some of the JVM parameters.  It&#039;s a whole new world over them thar hills.</description>
		<content:encoded><![CDATA[<p>Tight.  I love the black magic that you can get with some of the JVM parameters.  It&#39;s a whole new world over them thar hills.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
