<?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: Site Woes</title>
	<atom:link href="http://www.outsidethebeltway.com/archives/site_woes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.outsidethebeltway.com/archives/site_woes/</link>
	<description>Online Journal of Politics and Foreign Affairs</description>
	<lastBuildDate>Wed, 25 Nov 2009 08:01:21 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PoliBlog</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24131</link>
		<dc:creator>PoliBlog</dc:creator>
		<pubDate>Thu, 23 Sep 2004 12:46:58 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24131</guid>
		<description>&lt;strong&gt;Beheading, Morbid Curiousity and Psychobabble&lt;/strong&gt;
(Note:  I realized that I did not post the complete version of the post last night, so here it is--I have deleted the one I posted last night):

After noting the OTB traffic issue, I noticed this story on Google News:  1 million Web users click to se...</description>
		<content:encoded><![CDATA[<p><strong>Beheading, Morbid Curiousity and Psychobabble</strong><br />
(Note:  I realized that I did not post the complete version of the post last night, so here it is--I have deleted the one I posted last night):</p>
<p>After noting the OTB traffic issue, I noticed this story on Google News:  1 million Web users click to se...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. Minich, PI</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24126</link>
		<dc:creator>B. Minich, PI</dc:creator>
		<pubDate>Thu, 23 Sep 2004 04:03:55 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24126</guid>
		<description>(Note: this is why any changes to the site itself would require a rebuilding of all the files - they were static, whereas Wordpress is dynamic.  This is one of the advantages of the Wordpress method.)</description>
		<content:encoded><![CDATA[<p>(Note: this is why any changes to the site itself would require a rebuilding of all the files - they were static, whereas Wordpress is dynamic.  This is one of the advantages of the Wordpress method.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. Minich, PI</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24125</link>
		<dc:creator>B. Minich, PI</dc:creator>
		<pubDate>Thu, 23 Sep 2004 04:02:36 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24125</guid>
		<description>Well, the &quot;MySQL was maxing out&quot; makes more sense than bandwidth issues, which should be easily handled by the server.

The main difference between Wordpress and Movable Type is that Movable Type would make a new index page after you posted a new entry, and be done with it.  Also, all archive links were generated when you posted.  Thus, after updating the database, SQL (the program that keeps your information) wasn&#039;t utilized that much.  I think it was checked when you loaded the index page, but if you clicked a specific page (like someone looking up a beheading article), the database wasn&#039;t checked at all.

In the case of Wordpress, the pages are generated on the fly.  Thus, a spike in bandwidth causes a spike in SQL activity, which probably explains your problems.  There are advantages and disadvantages to both of these methods.

Did your SQL database ever go down when you were running Movable Type?  If it ever did (as mine did once), the pages still worked, because they had been generated and saved as individual files - the measure that saved looking things up in the database.  Wordpress does not do this - no matter how you specify things, the pages are loaded through the &quot;index.php&quot; file you use to start the site.

I do find it interesting that the site went down, though, as most web programs today that use SQL databases use the Wordpress method - you&#039;d figure hosts would be ready for it.  Anyway, I hope things work out.

I tried to &quot;non-techify&quot; that explaination, and wouldn&#039;t be surprised if I failed.  Hopefully, this leads to at least a slightly better understanding of the problem.</description>
		<content:encoded><![CDATA[<p>Well, the "MySQL was maxing out" makes more sense than bandwidth issues, which should be easily handled by the server.</p>
<p>The main difference between Wordpress and Movable Type is that Movable Type would make a new index page after you posted a new entry, and be done with it.  Also, all archive links were generated when you posted.  Thus, after updating the database, SQL (the program that keeps your information) wasn't utilized that much.  I think it was checked when you loaded the index page, but if you clicked a specific page (like someone looking up a beheading article), the database wasn't checked at all.</p>
<p>In the case of Wordpress, the pages are generated on the fly.  Thus, a spike in bandwidth causes a spike in SQL activity, which probably explains your problems.  There are advantages and disadvantages to both of these methods.</p>
<p>Did your SQL database ever go down when you were running Movable Type?  If it ever did (as mine did once), the pages still worked, because they had been generated and saved as individual files - the measure that saved looking things up in the database.  Wordpress does not do this - no matter how you specify things, the pages are loaded through the "index.php" file you use to start the site.</p>
<p>I do find it interesting that the site went down, though, as most web programs today that use SQL databases use the Wordpress method - you'd figure hosts would be ready for it.  Anyway, I hope things work out.</p>
<p>I tried to "non-techify" that explaination, and wouldn't be surprised if I failed.  Hopefully, this leads to at least a slightly better understanding of the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Prather</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24124</link>
		<dc:creator>Robert Prather</dc:creator>
		<pubDate>Thu, 23 Sep 2004 03:54:31 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24124</guid>
		<description>I don&#039;t know exactly why it happened, I was just mentioning that I didn&#039;t have inline comments to add to the comment above.  In other words, I don&#039;t think they are the issue.  It took a few weeks before the problem materialized.  All I&#039;m saying.</description>
		<content:encoded><![CDATA[<p>I don't know exactly why it happened, I was just mentioning that I didn't have inline comments to add to the comment above.  In other words, I don't think they are the issue.  It took a few weeks before the problem materialized.  All I'm saying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Joyner</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24123</link>
		<dc:creator>James Joyner</dc:creator>
		<pubDate>Thu, 23 Sep 2004 03:36:24 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24123</guid>
		<description>Interesting.  Of course, I&#039;ve had inline comments for months with no problems until now.</description>
		<content:encoded><![CDATA[<p>Interesting.  Of course, I've had inline comments for months with no problems until now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Prather</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24122</link>
		<dc:creator>Robert Prather</dc:creator>
		<pubDate>Thu, 23 Sep 2004 03:20:57 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24122</guid>
		<description>I had the identical problem with a different host once I switched to WP.  The host went ballistic and I had to switch; they weren&#039;t nearly as nice about it and made me sound like a pornographer with their warning message, which referenced objectionable content without explaining it was a resource issue on their server.  Almost identical and I didn&#039;t have inline comments of any kind.</description>
		<content:encoded><![CDATA[<p>I had the identical problem with a different host once I switched to WP.  The host went ballistic and I had to switch; they weren't nearly as nice about it and made me sound like a pornographer with their warning message, which referenced objectionable content without explaining it was a resource issue on their server.  Almost identical and I didn't have inline comments of any kind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24121</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Thu, 23 Sep 2004 03:12:40 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24121</guid>
		<description>I suspect that each and every inline comment is causing a database query when the page is assembled, rather than when someone decides to check the comments to a specific post.  Possibly every post on the front page also causes a database query, but that&#039;s a lot easier to cache.</description>
		<content:encoded><![CDATA[<p>I suspect that each and every inline comment is causing a database query when the page is assembled, rather than when someone decides to check the comments to a specific post.  Possibly every post on the front page also causes a database query, but that's a lot easier to cache.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PoliBlog</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24120</link>
		<dc:creator>PoliBlog</dc:creator>
		<pubDate>Thu, 23 Sep 2004 02:46:13 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24120</guid>
		<description>&lt;strong&gt;Beheadings and Morbid Curiousity&lt;/strong&gt;
After noting the OTB traffic issue, I noticed this story on Google News:  1 million Web users click to see beheading / 50,000 an hour visit site to see U.S. captive&#039;s slaughterDan Klinker operates a Web site carrying Monday&#039;s video of a hooded man cu...</description>
		<content:encoded><![CDATA[<p><strong>Beheadings and Morbid Curiousity</strong><br />
After noting the OTB traffic issue, I noticed this story on Google News:  1 million Web users click to see beheading / 50,000 an hour visit site to see U.S. captive's slaughterDan Klinker operates a Web site carrying Monday's video of a hooded man cu...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PoliBlog</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24119</link>
		<dc:creator>PoliBlog</dc:creator>
		<pubDate>Thu, 23 Sep 2004 02:11:47 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24119</guid>
		<description>&lt;strong&gt;Back in Business (I Hope)&lt;/strong&gt;
Weird goings-ons with Hosting Matters today, as noted below.  For while the site was down, then I could get on, but couldn&#039;t post, and then areound 4:45 I was getting a MySQL error and nothing would come up.  I had to head out to church, so wasn&#039;t ab...</description>
		<content:encoded><![CDATA[<p><strong>Back in Business (I Hope)</strong><br />
Weird goings-ons with Hosting Matters today, as noted below.  For while the site was down, then I could get on, but couldn't post, and then areound 4:45 I was getting a MySQL error and nothing would come up.  I had to head out to church, so wasn't ab...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tiger</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24116</link>
		<dc:creator>Tiger</dc:creator>
		<pubDate>Thu, 23 Sep 2004 00:53:28 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24116</guid>
		<description>I have experienced a pretty big spike over the last couple of days myself from Google searches for the Berg matter, although, it is also nowhere near as big as the one I got right after the event.</description>
		<content:encoded><![CDATA[<p>I have experienced a pretty big spike over the last couple of days myself from Google searches for the Berg matter, although, it is also nowhere near as big as the one I got right after the event.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joy</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24115</link>
		<dc:creator>joy</dc:creator>
		<pubDate>Thu, 23 Sep 2004 00:40:33 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24115</guid>
		<description>James, 

You&#039;re actually quite lucky. More than a few admins I know would have booted you off of their servers without explanation.  

Anyway, from your snippets, I&#039;m guessing that the database is being queried for those 15 or so posts all at once.  As far as I understand it, each time a person requests a page your database is being queried.    

So, instead of having the problems of having one popular post linked (which i think would be cached), you have people trying to get to 15 different posts, which is a drain on the database.

Also, you&#039;re on WP, so that too could be contributing to your issues...</description>
		<content:encoded><![CDATA[<p>James, </p>
<p>You're actually quite lucky. More than a few admins I know would have booted you off of their servers without explanation.  </p>
<p>Anyway, from your snippets, I'm guessing that the database is being queried for those 15 or so posts all at once.  As far as I understand it, each time a person requests a page your database is being queried.    </p>
<p>So, instead of having the problems of having one popular post linked (which i think would be cached), you have people trying to get to 15 different posts, which is a drain on the database.</p>
<p>Also, you're on WP, so that too could be contributing to your issues...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob's Place</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24105</link>
		<dc:creator>Bob's Place</dc:creator>
		<pubDate>Wed, 22 Sep 2004 19:33:26 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24105</guid>
		<description>&lt;strong&gt;International misunderstanding&lt;/strong&gt;
 Found on the Braden Files today, this article by Dr George Friedman on Stratfor.com from 9/14/04 certainly puts the international mis-understanding of the USA in proper perspective , and accurately describes the positions of both our &quot;friends&quot; and ...</description>
		<content:encoded><![CDATA[<p><strong>International misunderstanding</strong><br />
 Found on the Braden Files today, this article by Dr George Friedman on Stratfor.com from 9/14/04 certainly puts the international mis-understanding of the USA in proper perspective , and accurately describes the positions of both our "friends" and ...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OF Jay</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24104</link>
		<dc:creator>OF Jay</dc:creator>
		<pubDate>Wed, 22 Sep 2004 19:30:34 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24104</guid>
		<description>Not even Instapundit could crash a WP-powered blog on a decent enough server---which I believe HM&#039;s are---so I was quite surprised with the whole b3heading search surge causing CPU overuse.

There&#039;s a diff. between CPU load and server traffic load. The former is a bigger PITA for server admins; there is the &lt;a href=&quot;http://photomatt.net/2004/06/13/staticize-reloaded&quot;&gt;staticize plugin&lt;/a&gt; for WP that can help alleviate these problems, although I wouldn&#039;t know, for the life of me, how to go about implementing it.</description>
		<content:encoded><![CDATA[<p>Not even Instapundit could crash a WP-powered blog on a decent enough server---which I believe HM's are---so I was quite surprised with the whole b3heading search surge causing CPU overuse.</p>
<p>There's a diff. between CPU load and server traffic load. The former is a bigger PITA for server admins; there is the <a href="http://photomatt.net/2004/06/13/staticize-reloaded">staticize plugin</a> for WP that can help alleviate these problems, although I wouldn't know, for the life of me, how to go about implementing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PoliBlog</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24103</link>
		<dc:creator>PoliBlog</dc:creator>
		<pubDate>Wed, 22 Sep 2004 19:12:25 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24103</guid>
		<description>&lt;strong&gt;Overtaxing the Servers&lt;/strong&gt;
As Paul noted earlier, PoliBlog was down for a bit earlier today.

Now it appears that it was all OTB&#039;s fault.  Although, I am with James:  I don&#039;t quite get what caused the problem--the initial Berg beheading traffic was bigger than this--I think ...</description>
		<content:encoded><![CDATA[<p><strong>Overtaxing the Servers</strong><br />
As Paul noted earlier, PoliBlog was down for a bit earlier today.</p>
<p>Now it appears that it was all OTB's fault.  Although, I am with James:  I don't quite get what caused the problem--the initial Berg beheading traffic was bigger than this--I think ...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wizbang</title>
		<link>http://www.outsidethebeltway.com/archives/site_woes/comment-page-1/#comment-24102</link>
		<dc:creator>Wizbang</dc:creator>
		<pubDate>Wed, 22 Sep 2004 19:04:07 +0000</pubDate>
		<guid isPermaLink="false">/?p=7524#comment-24102</guid>
		<description>&lt;strong&gt;Do we need a fund rasier?&lt;/strong&gt;
Looks like James Joyner must have fallen on hard times. Hey, someone had to rib him about it. Update: He must have paid the bill pretty quick, he&#039;s back now. Update 2: Now the site is gone and so is...</description>
		<content:encoded><![CDATA[<p><strong>Do we need a fund rasier?</strong><br />
Looks like James Joyner must have fallen on hard times. Hey, someone had to rib him about it. Update: He must have paid the bill pretty quick, he's back now. Update 2: Now the site is gone and so is...</p>
]]></content:encoded>
	</item>
</channel>
</rss>
