<?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: Anatomy of a Fireballing</title>
	<atom:link href="http://blog.23x.net/216/anatomy-of-a-fireballing.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html</link>
	<description>News you didn't know you needed</description>
	<lastBuildDate>Mon, 06 Sep 2010 22:10:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Links for 8-9-2010 &#124; Sue Cline</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-4648</link>
		<dc:creator>Links for 8-9-2010 &#124; Sue Cline</dc:creator>
		<pubDate>Mon, 09 Aug 2010 23:30:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-4648</guid>
		<description>[...] get Fireballed: great ode to WP-Super Cache, which we support, and includes links to Anatomy of a Fireballing &#8211; I love these analytical breakdowns so we can help our clients be prepared for internet [...]</description>
		<content:encoded><![CDATA[<p>[...] get Fireballed: great ode to WP-Super Cache, which we support, and includes links to Anatomy of a Fireballing &#8211; I love these analytical breakdowns so we can help our clients be prepared for internet [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Betteridge</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-4522</link>
		<dc:creator>Ian Betteridge</dc:creator>
		<pubDate>Tue, 09 Mar 2010 20:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-4522</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;@cimota If you&#039;re on Wordpress, some good advice from @jearle at http://blog.23x.net/216/anatomy-of-a-fireballing.html&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">@cimota If you&#39;re on WordPress, some good advice from @jearle at <a href="http://blog.23x.net/216/anatomy-of-a-fireballing.html" rel="nofollow">http://blog.23x.net/216/anatomy-of-a-fireballing.html</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Burleson</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-4523</link>
		<dc:creator>Patrick Burleson</dc:creator>
		<pubDate>Thu, 18 Feb 2010 23:45:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-4523</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;@danwood @gruber will knock your server around pretty good. http://blog.23x.net/216/anatomy-of-a-fireballing.html&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">@danwood @gruber will knock your server around pretty good. <a href="http://blog.23x.net/216/anatomy-of-a-fireballing.html" rel="nofollow">http://blog.23x.net/216/anatomy-of-a-fireballing.html</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew McLellan</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-4524</link>
		<dc:creator>Drew McLellan</dc:creator>
		<pubDate>Mon, 14 Dec 2009 23:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-4524</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Man Goes from No Traffic to Some Traffic. WordPress Dies. http://blog.23x.net/216/anatomy-of-a-fireballing.html (Seriously, WP?)&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Man Goes from No Traffic to Some Traffic. WordPress Dies. <a href="http://blog.23x.net/216/anatomy-of-a-fireballing.html" rel="nofollow">http://blog.23x.net/216/anatomy-of-a-fireballing.html</a> (Seriously, WP?)</span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Jaquith</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-2648</link>
		<dc:creator>Mark Jaquith</dc:creator>
		<pubDate>Wed, 09 Dec 2009 22:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-2648</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-2620&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-2620&quot; rel=&quot;nofollow&quot;&gt;Dave&lt;/a&gt; :&lt;/strong&gt;
My question is this – why is Wordpress by itself so inefficient at caching pages? It seems silly to me that a default install is so un-resiliant as to bring down a server if it gets a lot of views, which is just about everyone’s goal. It seems there should be a better caching component, with the ability to turn off for debugging, within the core WP code.
&lt;/blockquote&gt;

Because it has to run on the least common denominator setup. We can&#039;t rely on Memcached, APC, Xcache or even the filesystem. As someone mentioned above, some hosts don&#039;t want you to use WP-Super-Cache, probably because they have a distributed filesystem and all those file writes are going to mess things up.

This is a good problem to have, but it&#039;s not one that a lot of WordPress users ever have to worry about. It just seems like it is. You don&#039;t notice the 10 million WordPress blogs that handle their load without breaking a sweat. You notice the ones you click to from Digg or Daring Fireball. If you look at the 80/20 thing, it&#039;s probably not even 1 percent — forget 20 percent or 80 percent.

We are talking a lot about the idea of &quot;canonical plugins&quot; — plugins that are featured from with WordPress, are well-supported, secure, stay up-to-date. &quot;Caching&quot; is definitely one of the areas we think could benefit from a canonical caching plugin (and until then, WP-Super-Cache is probably the right choice for most people on shared hosting).</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-2620"><p>
<strong><a href="#comment-2620" rel="nofollow">Dave</a> :</strong><br />
My question is this – why is WordPress by itself so inefficient at caching pages? It seems silly to me that a default install is so un-resiliant as to bring down a server if it gets a lot of views, which is just about everyone’s goal. It seems there should be a better caching component, with the ability to turn off for debugging, within the core WP code.
</p></blockquote>
<p>Because it has to run on the least common denominator setup. We can&#8217;t rely on Memcached, APC, Xcache or even the filesystem. As someone mentioned above, some hosts don&#8217;t want you to use WP-Super-Cache, probably because they have a distributed filesystem and all those file writes are going to mess things up.</p>
<p>This is a good problem to have, but it&#8217;s not one that a lot of WordPress users ever have to worry about. It just seems like it is. You don&#8217;t notice the 10 million WordPress blogs that handle their load without breaking a sweat. You notice the ones you click to from Digg or Daring Fireball. If you look at the 80/20 thing, it&#8217;s probably not even 1 percent — forget 20 percent or 80 percent.</p>
<p>We are talking a lot about the idea of &#8220;canonical plugins&#8221; — plugins that are featured from with WordPress, are well-supported, secure, stay up-to-date. &#8220;Caching&#8221; is definitely one of the areas we think could benefit from a canonical caching plugin (and until then, WP-Super-Cache is probably the right choice for most people on shared hosting).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-2643</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Wed, 09 Dec 2009 11:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-2643</guid>
		<description>&lt;a href=&quot;#comment-2565&quot; rel=&quot;nofollow&quot;&gt;@David Chin&lt;/a&gt; 
I&#039;ve had that happen a few times as well after a spike. Hostgator at least help you through the process of installing supercache or something a bit meatier if that doesn&#039;t work out.</description>
		<content:encoded><![CDATA[<p><a href="#comment-2565" rel="nofollow">@David Chin</a><br />
I&#8217;ve had that happen a few times as well after a spike. Hostgator at least help you through the process of installing supercache or something a bit meatier if that doesn&#8217;t work out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hedirman Supian</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-4525</link>
		<dc:creator>Hedirman Supian</dc:creator>
		<pubDate>Wed, 09 Dec 2009 03:18:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-4525</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;@patlaw Thought of installing wp-super-cache? Might help till u get tt dedicated server http://bit.ly/8oYNA7&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">@patlaw Thought of installing wp-super-cache? Might help till u get tt dedicated server <a href="http://bit.ly/8oYNA7" rel="nofollow">http://bit.ly/8oYNA7</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Earle</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-2621</link>
		<dc:creator>Jared Earle</dc:creator>
		<pubDate>Sun, 06 Dec 2009 18:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-2621</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-2620&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-2620&quot; rel=&quot;nofollow&quot;&gt;Dave&lt;/a&gt; :&lt;/strong&gt;
&lt;p&gt;My question is this – why is Wordpress by itself so inefficient at caching pages? &lt;/p&gt;
&lt;/blockquote&gt;
I suspect it&#039;s because of the widgets: widgets make a stupid amount of SQL calls and, if you&#039;re not running memcached or similar, it&#039;s SQL that fails first. What WP should do is have WP-Super-Cache as part of the default install, turned off or at a safe level.</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-2620"><p>
<strong><a href="#comment-2620" rel="nofollow">Dave</a> :</strong></p>
<p>My question is this – why is WordPress by itself so inefficient at caching pages? </p>
</blockquote>
<p>I suspect it&#8217;s because of the widgets: widgets make a stupid amount of SQL calls and, if you&#8217;re not running memcached or similar, it&#8217;s SQL that fails first. What WP should do is have WP-Super-Cache as part of the default install, turned off or at a safe level.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-2620</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sun, 06 Dec 2009 17:39:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-2620</guid>
		<description>Nice post on Wp-super-cache. I use it on my own site which handles the occasional spikes well. As soon as I take it off, my blog will essentially take down the server. Fun huh?

My question is this - why is Wordpress by itself so inefficient at caching pages? It seems silly to me that a default install is so un-resiliant as to bring down a server if it gets a lot of views, which is just about everyone&#039;s goal. It seems there should be a better caching component, with the ability to turn off for debugging, within the core WP code.

Thanks again.</description>
		<content:encoded><![CDATA[<p>Nice post on Wp-super-cache. I use it on my own site which handles the occasional spikes well. As soon as I take it off, my blog will essentially take down the server. Fun huh?</p>
<p>My question is this &#8211; why is WordPress by itself so inefficient at caching pages? It seems silly to me that a default install is so un-resiliant as to bring down a server if it gets a lot of views, which is just about everyone&#8217;s goal. It seems there should be a better caching component, with the ability to turn off for debugging, within the core WP code.</p>
<p>Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donncha O Caoimh</title>
		<link>http://blog.23x.net/216/anatomy-of-a-fireballing.html#comment-2606</link>
		<dc:creator>Donncha O Caoimh</dc:creator>
		<pubDate>Thu, 03 Dec 2009 22:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.23x.net/?p=216#comment-2606</guid>
		<description>&lt;a href=&quot;#comment-2594&quot; rel=&quot;nofollow&quot;&gt;@Hty&lt;/a&gt; Blogs at WordPress.com will easily handle the traffic from Fireball, no problem at all. Site wouldn&#039;t even notice it.

&lt;a href=&quot;#comment-2593&quot; rel=&quot;nofollow&quot;&gt;@Skirkster&lt;/a&gt; - do they use NFS to host their sites? That might be why they don&#039;t recommend it.</description>
		<content:encoded><![CDATA[<p><a href="#comment-2594" rel="nofollow">@Hty</a> Blogs at WordPress.com will easily handle the traffic from Fireball, no problem at all. Site wouldn&#8217;t even notice it.</p>
<p><a href="#comment-2593" rel="nofollow">@Skirkster</a> &#8211; do they use NFS to host their sites? That might be why they don&#8217;t recommend it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
