<?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: Ruby leaks memory</title>
	<atom:link href="http://pennysmalls.com/2008/03/23/ruby-leaks-memory/feed/" rel="self" type="application/rss+xml" />
	<link>http://pennysmalls.com/2008/03/23/ruby-leaks-memory/</link>
	<description>A blog about Ruby, Rails and other tech.  Mostly.</description>
	<lastBuildDate>Wed, 25 Nov 2009 03:12:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stephen Sykes</title>
		<link>http://pennysmalls.com/2008/03/23/ruby-leaks-memory/comment-page-1/#comment-174</link>
		<dc:creator>Stephen Sykes</dc:creator>
		<pubDate>Thu, 21 Aug 2008 21:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2008/03/23/ruby-leaks-memory/#comment-174</guid>
		<description>Yes, we use OS X for dev, and so far I have been unable to compile ruby 1.8.7 with tcmalloc on that platform.

However, it does compile ok on our x86-64 app server, but I have yet to complete testing with it so I haven&#039;t run it live so far.  I hear that performance is significantly improved with tcmalloc, but  I don&#039;t expect memory usage improvements.</description>
		<content:encoded><![CDATA[<p>Yes, we use OS X for dev, and so far I have been unable to compile ruby 1.8.7 with tcmalloc on that platform.</p>
<p>However, it does compile ok on our x86-64 app server, but I have yet to complete testing with it so I haven&#8217;t run it live so far.  I hear that performance is significantly improved with tcmalloc, but  I don&#8217;t expect memory usage improvements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roger</title>
		<link>http://pennysmalls.com/2008/03/23/ruby-leaks-memory/comment-page-1/#comment-173</link>
		<dc:creator>roger</dc:creator>
		<pubDate>Thu, 21 Aug 2008 18:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2008/03/23/ruby-leaks-memory/#comment-173</guid>
		<description>I wonder if tcmalloc would help, too. [i.e. it&#039;s also out there and seems to work well, perhaps without some of the drawbacks of ptmalloc3 + ruby].  

It won&#039;t work on OS X but on Linux it does.</description>
		<content:encoded><![CDATA[<p>I wonder if tcmalloc would help, too. [i.e. it's also out there and seems to work well, perhaps without some of the drawbacks of ptmalloc3 + ruby].  </p>
<p>It won&#8217;t work on OS X but on Linux it does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roger degree search</title>
		<link>http://pennysmalls.com/2008/03/23/ruby-leaks-memory/comment-page-1/#comment-100</link>
		<dc:creator>roger degree search</dc:creator>
		<pubDate>Thu, 03 Jul 2008 18:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2008/03/23/ruby-leaks-memory/#comment-100</guid>
		<description>I believe it&#039;s fixed in 1.8.6/1.8.7 SVN [if not a released version].</description>
		<content:encoded><![CDATA[<p>I believe it&#8217;s fixed in 1.8.6/1.8.7 SVN [if not a released version].</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Sykes</title>
		<link>http://pennysmalls.com/2008/03/23/ruby-leaks-memory/comment-page-1/#comment-90</link>
		<dc:creator>Stephen Sykes</dc:creator>
		<pubDate>Mon, 26 May 2008 07:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2008/03/23/ruby-leaks-memory/#comment-90</guid>
		<description>It&#039;s a relief to see that this memory leak appears to be fixed in Ruby 1.8.7 preview 4.

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/302887</description>
		<content:encoded><![CDATA[<p>It&#8217;s a relief to see that this memory leak appears to be fixed in Ruby 1.8.7 preview 4.</p>
<p><a href="http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/302887" rel="nofollow">http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/302887</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Sykes</title>
		<link>http://pennysmalls.com/2008/03/23/ruby-leaks-memory/comment-page-1/#comment-37</link>
		<dc:creator>Stephen Sykes</dc:creator>
		<pubDate>Sun, 23 Mar 2008 21:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2008/03/23/ruby-leaks-memory/#comment-37</guid>
		<description>This is Ruby 1.8.6 p114.  We are certainly not seeing pauses due to GC running, so I suspect that we are not hitting quite the same problems that you had.</description>
		<content:encoded><![CDATA[<p>This is Ruby 1.8.6 p114.  We are certainly not seeing pauses due to GC running, so I suspect that we are not hitting quite the same problems that you had.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zeno Davatz</title>
		<link>http://pennysmalls.com/2008/03/23/ruby-leaks-memory/comment-page-1/#comment-36</link>
		<dc:creator>Zeno Davatz</dc:creator>
		<pubDate>Sun, 23 Mar 2008 21:24:22 +0000</pubDate>
		<guid isPermaLink="false">http://pennysmalls.com/2008/03/23/ruby-leaks-memory/#comment-36</guid>
		<description>Interesting! Keep us posted. We are a lot more stable since we compiled against &quot;ptmalloc3&quot; - Which version of Ruby are you using?

Best
Zeno</description>
		<content:encoded><![CDATA[<p>Interesting! Keep us posted. We are a lot more stable since we compiled against &#8220;ptmalloc3&#8243; &#8211; Which version of Ruby are you using?</p>
<p>Best<br />
Zeno</p>
]]></content:encoded>
	</item>
</channel>
</rss>
