<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Memory will be the real performance bottleneck on your VPS</title>
	<atom:link href="http://plasticboy.com/archives/2009/11/30/memory-will-be-the-real-performance-bottleneck-on-your-vps/feed/" rel="self" type="application/rss+xml" />
	<link>http://plasticboy.com/archives/2009/11/30/memory-will-be-the-real-performance-bottleneck-on-your-vps/</link>
	<description>Ben Williams&#039; blog about technology, Linux, digital music, Rhapsody, veganism, and a little politics.</description>
	<lastBuildDate>Fri, 02 Sep 2011 19:55:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: afternoon</title>
		<link>http://plasticboy.com/archives/2009/11/30/memory-will-be-the-real-performance-bottleneck-on-your-vps/comment-page-1/#comment-68104</link>
		<dc:creator>afternoon</dc:creator>
		<pubDate>Mon, 08 Mar 2010 13:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://plasticboy.com/?p=3495#comment-68104</guid>
		<description>&lt;p&gt;I highly recommend a combination of nginx and FastCGI. I&#039;m personally running both PHP and Python (Django) on a single Linode. I have 3 php-cgi instances resident at about 20MB each. nginx is resident at 2MB. Although the RAM usage is not much different, nginx serves static content, so the PHP processes service far fewer requests, raising the requests/sec limit.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I highly recommend a combination of nginx and FastCGI. I&#8217;m personally running both PHP and Python (Django) on a single Linode. I have 3 php-cgi instances resident at about 20MB each. nginx is resident at 2MB. Although the RAM usage is not much different, nginx serves static content, so the PHP processes service far fewer requests, raising the requests/sec limit.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: How to handle 1000&#8217;s of concurrent users on a 360MB VPS</title>
		<link>http://plasticboy.com/archives/2009/11/30/memory-will-be-the-real-performance-bottleneck-on-your-vps/comment-page-1/#comment-64777</link>
		<dc:creator>How to handle 1000&#8217;s of concurrent users on a 360MB VPS</dc:creator>
		<pubDate>Tue, 01 Dec 2009 20:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://plasticboy.com/?p=3495#comment-64777</guid>
		<description>&lt;p&gt;[...] has been some recent confusion about how much memory you need in a web server to handle a huge number of concurrent requests. I [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] has been some recent confusion about how much memory you need in a web server to handle a huge number of concurrent requests. I [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://plasticboy.com/archives/2009/11/30/memory-will-be-the-real-performance-bottleneck-on-your-vps/comment-page-1/#comment-64775</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 01 Dec 2009 16:46:34 +0000</pubDate>
		<guid isPermaLink="false">http://plasticboy.com/?p=3495#comment-64775</guid>
		<description>&lt;p&gt;Nice analysis, David. I wasn&#039;t aware of the memory cost of 64 bit.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nice analysis, David. I wasn&#8217;t aware of the memory cost of 64 bit.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: davidw</title>
		<link>http://plasticboy.com/archives/2009/11/30/memory-will-be-the-real-performance-bottleneck-on-your-vps/comment-page-1/#comment-64771</link>
		<dc:creator>davidw</dc:creator>
		<pubDate>Tue, 01 Dec 2009 13:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://plasticboy.com/?p=3495#comment-64771</guid>
		<description>&lt;p&gt;Linode does pretty well in terms of memory usage, because it lets you choose 32 bit, as opposed to 64 bit (like Slicehost).  I did some numbers of my own a while back, and while those were the only two I compared, Linode really won out:&lt;/p&gt;

&lt;p&gt;http://journal.dedasys.com/2008/11/24/slicehost-vs-linode&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Linode does pretty well in terms of memory usage, because it lets you choose 32 bit, as opposed to 64 bit (like Slicehost).  I did some numbers of my own a while back, and while those were the only two I compared, Linode really won out:</p>

<p><a href="http://journal.dedasys.com/2008/11/24/slicehost-vs-linode" rel="nofollow nofollow">http://journal.dedasys.com/2008/11/24/slicehost-vs-linode</a></p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: plasticboy.com @ 2012-02-09 07:15:48 -->
