<?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 web server performance</title>
	<atom:link href="http://ariekanarie.nl/archives/44/ruby-web-server-performance/feed" rel="self" type="application/rss+xml" />
	<link>http://ariekanarie.nl/archives/44/ruby-web-server-performance</link>
	<description></description>
	<lastBuildDate>Fri, 30 Mar 2012 11:56:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: mod_rails vs thin vs ebb vs mongrel &#124; Arie&#8217;s Blog</title>
		<link>http://ariekanarie.nl/archives/44/ruby-web-server-performance/comment-page-1#comment-273</link>
		<dc:creator>mod_rails vs thin vs ebb vs mongrel &#124; Arie&#8217;s Blog</dc:creator>
		<pubDate>Wed, 16 Apr 2008 09:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://ariekanarie.nl/archives/142/ruby-on-rails-performance#comment-273</guid>
		<description>[...] the recent release of mod_rails, I thought it was time for yet another benchmark. Mod_rails aims to make deployment of RubyOnRails applications comparable to deploying a [...]</description>
		<content:encoded><![CDATA[<p>[...] the recent release of mod_rails, I thought it was time for yet another benchmark. Mod_rails aims to make deployment of RubyOnRails applications comparable to deploying a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arie</title>
		<link>http://ariekanarie.nl/archives/44/ruby-web-server-performance/comment-page-1#comment-243</link>
		<dc:creator>Arie</dc:creator>
		<pubDate>Thu, 20 Mar 2008 13:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://ariekanarie.nl/archives/142/ruby-on-rails-performance#comment-243</guid>
		<description>The tests were done on a Dell D830 with Intel T7300CPU, 7200RPM disk and 2GB of RAM.

The data was fetched from DB once, and from than on it was fragment cached. The only query left at that point was the one checking for the currently logged in user.</description>
		<content:encoded><![CDATA[<p>The tests were done on a Dell D830 with Intel T7300CPU, 7200RPM disk and 2GB of RAM.</p>
<p>The data was fetched from DB once, and from than on it was fragment cached. The only query left at that point was the one checking for the currently logged in user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Glasgow</title>
		<link>http://ariekanarie.nl/archives/44/ruby-web-server-performance/comment-page-1#comment-242</link>
		<dc:creator>Thomas Glasgow</dc:creator>
		<pubDate>Thu, 20 Mar 2008 13:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://ariekanarie.nl/archives/142/ruby-on-rails-performance#comment-242</guid>
		<description>Hi,

Can you provide the hardware specs please?

And also, the page you test against, does it fetch its data from the DB or is it hardcoded in a view and/or controller?

My benchmarks resulted in 2x less performance when my application connects to the DB.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Can you provide the hardware specs please?</p>
<p>And also, the page you test against, does it fetch its data from the DB or is it hardcoded in a view and/or controller?</p>
<p>My benchmarks resulted in 2x less performance when my application connects to the DB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arie&#8217;s blog &#187; Blog Archive &#187; Yet another Ruby server</title>
		<link>http://ariekanarie.nl/archives/44/ruby-web-server-performance/comment-page-1#comment-240</link>
		<dc:creator>Arie&#8217;s blog &#187; Blog Archive &#187; Yet another Ruby server</dc:creator>
		<pubDate>Tue, 04 Mar 2008 16:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://ariekanarie.nl/archives/142/ruby-on-rails-performance#comment-240</guid>
		<description>[...] my benchmark I used the same application I used for my previous benchmark, only this time I benchmarked some extra [...]</description>
		<content:encoded><![CDATA[<p>[...] my benchmark I used the same application I used for my previous benchmark, only this time I benchmarked some extra [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

