<?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: Top scalability&#160;mistakes</title>
	<atom:link href="http://www.moskalyuk.com/blog/top-scalability-mistakes/1563/feed" rel="self" type="application/rss+xml" />
	<link>http://www.moskalyuk.com/blog/top-scalability-mistakes/1563</link>
	<description></description>
	<lastBuildDate>Wed, 02 Dec 2009 02:18:44 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Interesting Finds: 2008.07.30~2008.08.01 - gOODiDEA.NET</title>
		<link>http://www.moskalyuk.com/blog/top-scalability-mistakes/1563/comment-page-1#comment-707735</link>
		<dc:creator>Interesting Finds: 2008.07.30~2008.08.01 - gOODiDEA.NET</dc:creator>
		<pubDate>Thu, 31 Jul 2008 23:57:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.moskalyuk.com/blog/top-scalability-mistakes/1563#comment-707735</guid>
		<description>[...] Top scalability mistakes [...]</description>
		<content:encoded><![CDATA[<p>[...] Top scalability mistakes [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sufehmi</title>
		<link>http://www.moskalyuk.com/blog/top-scalability-mistakes/1563/comment-page-1#comment-707433</link>
		<dc:creator>sufehmi</dc:creator>
		<pubDate>Wed, 30 Jul 2008 12:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.moskalyuk.com/blog/top-scalability-mistakes/1563#comment-707433</guid>
		<description>&lt;i&gt;Use Ram Disks for any data that’s disposable&lt;/i&gt;

Can&#039;t believe anyone is STILL advocating this.

Edge servers are automatically behaving like Ram disk - only much, MUCH better; it uses the memory dynamically and in a way that&#039;s much manageable by the OS. Unlike Ram disk who&#039;s taking away the memory from the OS.

And edge servers WILL fallback to disk cache gracefully - therefore still giving excellent performance boost (because the request still doesn&#039;t hit the system). Unlike a Ram disk.</description>
		<content:encoded><![CDATA[<p><i>Use Ram Disks for any data that’s disposable</i></p>
<p>Can&#8217;t believe anyone is STILL advocating this.</p>
<p>Edge servers are automatically behaving like Ram disk &#8211; only much, MUCH better; it uses the memory dynamically and in a way that&#8217;s much manageable by the OS. Unlike Ram disk who&#8217;s taking away the memory from the OS.</p>
<p>And edge servers WILL fallback to disk cache gracefully &#8211; therefore still giving excellent performance boost (because the request still doesn&#8217;t hit the system). Unlike a Ram disk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sufehmi</title>
		<link>http://www.moskalyuk.com/blog/top-scalability-mistakes/1563/comment-page-1#comment-707432</link>
		<dc:creator>sufehmi</dc:creator>
		<pubDate>Wed, 30 Jul 2008 12:44:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.moskalyuk.com/blog/top-scalability-mistakes/1563#comment-707432</guid>
		<description>The top mistake should be : neglecting to use edge servers.

Edge server - also known as reverse-proxy server, provides the MOST significant scalability &amp; performance boost, by avoiding most requests to even hit the system.

Most of the requests won&#039;t even hit the webserver. Many will be served straight from memory. Some more from the disk cache (read: static files, further cached by the operating system)

In a case, a system was serving 2 requests per second at maximum, with 100% processor load. After deploying an edge server, it handles 500 requests per second, with 30% processor load.

The performance gain alone is simply mind-boggling. And it is scalable to the max - you can deploy multiple edge server, spreading the load between them. 

This is the top mistake, most definitely. Even so-called &quot;experts&quot; misses this : You START from the edge. From then you continue to the center of the architecture.</description>
		<content:encoded><![CDATA[<p>The top mistake should be : neglecting to use edge servers.</p>
<p>Edge server &#8211; also known as reverse-proxy server, provides the MOST significant scalability &amp; performance boost, by avoiding most requests to even hit the system.</p>
<p>Most of the requests won&#8217;t even hit the webserver. Many will be served straight from memory. Some more from the disk cache (read: static files, further cached by the operating system)</p>
<p>In a case, a system was serving 2 requests per second at maximum, with 100% processor load. After deploying an edge server, it handles 500 requests per second, with 30% processor load.</p>
<p>The performance gain alone is simply mind-boggling. And it is scalable to the max &#8211; you can deploy multiple edge server, spreading the load between them. </p>
<p>This is the top mistake, most definitely. Even so-called &#8220;experts&#8221; misses this : You START from the edge. From then you continue to the center of the architecture.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
