<?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: How to handle 1000&#8217;s of concurrent users on a 360MB VPS</title>
	<atom:link href="http://markmaunder.com/2009/how-to-handle-1000s-of-concurrent-users-on-a-360mb-vps/feed/" rel="self" type="application/rss+xml" />
	<link>http://markmaunder.com/2009/how-to-handle-1000s-of-concurrent-users-on-a-360mb-vps/</link>
	<description></description>
	<lastBuildDate>Fri, 30 Jul 2010 09:44:36 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stuart</title>
		<link>http://markmaunder.com/2009/how-to-handle-1000s-of-concurrent-users-on-a-360mb-vps/comment-page-1/#comment-949</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Sun, 20 Dec 2009 11:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://markmaunder.com/?p=430#comment-949</guid>
		<description>Why not just set up the server to run on Nginx from the start instead of bloating things with apache? You can easily get Nginx to spawn more worker processes. Our blog easily handles 10k+ Visits/day on a 360mb Linode without ever using more than 5% CPU :)</description>
		<content:encoded><![CDATA[<p>Why not just set up the server to run on Nginx from the start instead of bloating things with apache? You can easily get Nginx to spawn more worker processes. Our blog easily handles 10k+ Visits/day on a 360mb Linode without ever using more than 5% CPU <img src='http://markmaunder.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Adams</title>
		<link>http://markmaunder.com/2009/how-to-handle-1000s-of-concurrent-users-on-a-360mb-vps/comment-page-1/#comment-934</link>
		<dc:creator>Robert Adams</dc:creator>
		<pubDate>Wed, 02 Dec 2009 07:03:35 +0000</pubDate>
		<guid isPermaLink="false">http://markmaunder.com/?p=430#comment-934</guid>
		<description>I recently setup a VPS using Apache and have been load testing it to see what it&#039;s capable of. I knew about Nginx and using it as a reverse proxy to Apache, but I didn&#039;t know that it provided such a huge performance benefit. 

Truly great article. Thanks

One question though: Have you tested this configuration with Comet services at all? I suspect that it should work since, but just wondering if you had any first hand experiences.

Thanks again</description>
		<content:encoded><![CDATA[<p>I recently setup a VPS using Apache and have been load testing it to see what it&#8217;s capable of. I knew about Nginx and using it as a reverse proxy to Apache, but I didn&#8217;t know that it provided such a huge performance benefit. </p>
<p>Truly great article. Thanks</p>
<p>One question though: Have you tested this configuration with Comet services at all? I suspect that it should work since, but just wondering if you had any first hand experiences.</p>
<p>Thanks again</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://markmaunder.com/2009/how-to-handle-1000s-of-concurrent-users-on-a-360mb-vps/comment-page-1/#comment-933</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Wed, 02 Dec 2009 06:50:35 +0000</pubDate>
		<guid isPermaLink="false">http://markmaunder.com/?p=430#comment-933</guid>
		<description>lighttpd as a front end to a fastcgi app is the same basic design. You&#039;re putting a finite-state-machine designed web server that uses a single thread and can handle a huge number of concurrent connections in front of a one-thread-per-connection application server. 

Lighttpd vs Nginx is just personal preference. I haven&#039;t used Lighttpd enough to give you a good opinion on it but Nginx&#039;s configuration file is very flexible, it has some great modules, it can also run as multiple processes so that you can use all your CPU cores on a heavily loaded site. I&#039;ve been using Nginx in production and I regularly handle over 30,000 concurrent connections daily with nginx with hardly any server load (reverse proxying to apache).</description>
		<content:encoded><![CDATA[<p>lighttpd as a front end to a fastcgi app is the same basic design. You&#8217;re putting a finite-state-machine designed web server that uses a single thread and can handle a huge number of concurrent connections in front of a one-thread-per-connection application server. </p>
<p>Lighttpd vs Nginx is just personal preference. I haven&#8217;t used Lighttpd enough to give you a good opinion on it but Nginx&#8217;s configuration file is very flexible, it has some great modules, it can also run as multiple processes so that you can use all your CPU cores on a heavily loaded site. I&#8217;ve been using Nginx in production and I regularly handle over 30,000 concurrent connections daily with nginx with hardly any server load (reverse proxying to apache).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graeme</title>
		<link>http://markmaunder.com/2009/how-to-handle-1000s-of-concurrent-users-on-a-360mb-vps/comment-page-1/#comment-932</link>
		<dc:creator>Graeme</dc:creator>
		<pubDate>Wed, 02 Dec 2009 06:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://markmaunder.com/?p=430#comment-932</guid>
		<description>This may be a naive question: what is the advantage of this (and I know it is widely used) over, for example, Lighttpd with Fast CGI?</description>
		<content:encoded><![CDATA[<p>This may be a naive question: what is the advantage of this (and I know it is widely used) over, for example, Lighttpd with Fast CGI?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
