<?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: MySQL Table Locking &amp; WordPress Scalability</title>
	<atom:link href="http://www.allthingscahill.com/2008/07/mysql-table-locking-wordpress-scalability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allthingscahill.com/2008/07/mysql-table-locking-wordpress-scalability/</link>
	<description>The online home for Mark Cahill, and indeed, all things Cahill!</description>
	<lastBuildDate>Wed, 01 Sep 2010 16:15: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: Mark Cahill</title>
		<link>http://www.allthingscahill.com/2008/07/mysql-table-locking-wordpress-scalability/comment-page-1/#comment-1105</link>
		<dc:creator>Mark Cahill</dc:creator>
		<pubDate>Fri, 06 Mar 2009 13:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.allthingscahill.com/?p=540#comment-1105</guid>
		<description>We went through the code and made sure there were reasonable limits on what we were attempting to return.  Basically we found there were several &quot;select *
 from wp_posts&quot; querires that were then having 99% of the results trashed in the code that processed the them.  So simply adding a &quot;limit 10&quot; rather than returning everything then dumping it in the code later was the answer.

Best advice is to turn of slow query logging for a couple days and watch what turns up.  You&#039;ll see the same queries over and over again, and those are obviously the ones that need to be optimized if possible.  Add an index, etc.  

You hint at something I&#039;ve been meaning to do: get Glenn Nadeau to write a guest post on these types of issues.</description>
		<content:encoded><![CDATA[<p>We went through the code and made sure there were reasonable limits on what we were attempting to return.  Basically we found there were several &#8220;select *<br />
 from wp_posts&#8221; querires that were then having 99% of the results trashed in the code that processed the them.  So simply adding a &#8220;limit 10&#8243; rather than returning everything then dumping it in the code later was the answer.</p>
<p>Best advice is to turn of slow query logging for a couple days and watch what turns up.  You&#8217;ll see the same queries over and over again, and those are obviously the ones that need to be optimized if possible.  Add an index, etc.  </p>
<p>You hint at something I&#8217;ve been meaning to do: get Glenn Nadeau to write a guest post on these types of issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://www.allthingscahill.com/2008/07/mysql-table-locking-wordpress-scalability/comment-page-1/#comment-1104</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Fri, 06 Mar 2009 06:54:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.allthingscahill.com/?p=540#comment-1104</guid>
		<description>Did you make changes to the core to fix that? or just fixed the plugins?</description>
		<content:encoded><![CDATA[<p>Did you make changes to the core to fix that? or just fixed the plugins?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
