<?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"
	>
<channel>
	<title>Comments on: Thin, Ruby on Rails &#038; Nginx fair proxy: Performance testing</title>
	<atom:link href="http://www.misuse.org/science/2008/04/07/thin-ruby-on-rails-nginx-fair-proxy-performance-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.misuse.org/science/2008/04/07/thin-ruby-on-rails-nginx-fair-proxy-performance-testing/</link>
	<description>It would be a good idea.</description>
	<pubDate>Fri, 08 Aug 2008 00:41:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: science</title>
		<link>http://www.misuse.org/science/2008/04/07/thin-ruby-on-rails-nginx-fair-proxy-performance-testing/#comment-3500</link>
		<dc:creator>science</dc:creator>
		<pubDate>Fri, 13 Jun 2008 20:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2008/04/07/thin-ruby-on-rails-nginx-fair-proxy-performance-testing/#comment-3500</guid>
		<description>Mark: I'm running a pretty stock nginx config from EngineYard with just a few tweaks for page caching. You can get the nginx.conf from EY by booting their "express" version to see how their setup differs from yours:

http://express.engineyard.com/

I gave up on fair b/c my server responses are all reasonable even and the weird blockages you refer to were bugging me. I'm not sure what is causing them so I don't know if fail_timeouts would make a different or not. My only suggestion is to build an eval rig and put a test load on it in the various configs.</description>
		<content:encoded><![CDATA[<p>Mark: I&#8217;m running a pretty stock nginx config from EngineYard with just a few tweaks for page caching. You can get the nginx.conf from EY by booting their &#8220;express&#8221; version to see how their setup differs from yours:</p>
<p><a href="http://express.engineyard.com/" rel="nofollow">http://express.engineyard.com/</a></p>
<p>I gave up on fair b/c my server responses are all reasonable even and the weird blockages you refer to were bugging me. I&#8217;m not sure what is causing them so I don&#8217;t know if fail_timeouts would make a different or not. My only suggestion is to build an eval rig and put a test load on it in the various configs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Foster</title>
		<link>http://www.misuse.org/science/2008/04/07/thin-ruby-on-rails-nginx-fair-proxy-performance-testing/#comment-3499</link>
		<dc:creator>Mark Foster</dc:creator>
		<pubDate>Fri, 13 Jun 2008 20:32:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.misuse.org/science/2008/04/07/thin-ruby-on-rails-nginx-fair-proxy-performance-testing/#comment-3499</guid>
		<description>Interesting results. I wonder if you could share your nginx settings? We've also been using nginx+fair in front of mongrel and unsatisfied with the 'blockages' that are occurring. Is it better to use shorter fail_timeouts with fair?</description>
		<content:encoded><![CDATA[<p>Interesting results. I wonder if you could share your nginx settings? We&#8217;ve also been using nginx+fair in front of mongrel and unsatisfied with the &#8216;blockages&#8217; that are occurring. Is it better to use shorter fail_timeouts with fair?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
