<?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 &#8211; EXPLAIN Yourself</title>
	<atom:link href="http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/</link>
	<description>Welcome To The Planet's Weblog!</description>
	<lastBuildDate>Sat, 14 Nov 2009 22:33:20 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matthew</title>
		<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/comment-page-1/#comment-7383</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Thu, 11 Jun 2009 13:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.theplanet.com/?p=1100#comment-7383</guid>
		<description>AaronA:
 Yes, the improvement in performance is noticed everywhere. I&#039;ve seen queries that originally took several seconds go down to sub-second once a couple indexes where added.  The indexes, usually kept in memory, keep MySQL from having to access the disk which we all know is the slowest piece in a server.

Chris:
 I agree with you. If I really just wanted a raw count, I would have done a COUNT(*).  However, that wasn&#039;t the point of the article and that was the super-simple query I thought of to illustrate my point of the indexes.

 Also agreed, that if you give a dumb query it can help &quot;somewhat.&quot;  I hope you&#039;ll agree that an optimized &quot;dumb query&quot; is still better than a &quot;dumb query&quot; that does full-table scans or uses a disk-temp-table.</description>
		<content:encoded><![CDATA[<p>AaronA:<br />
 Yes, the improvement in performance is noticed everywhere. I&#8217;ve seen queries that originally took several seconds go down to sub-second once a couple indexes where added.  The indexes, usually kept in memory, keep MySQL from having to access the disk which we all know is the slowest piece in a server.</p>
<p>Chris:<br />
 I agree with you. If I really just wanted a raw count, I would have done a COUNT(*).  However, that wasn&#8217;t the point of the article and that was the super-simple query I thought of to illustrate my point of the indexes.</p>
<p> Also agreed, that if you give a dumb query it can help &#8220;somewhat.&#8221;  I hope you&#8217;ll agree that an optimized &#8220;dumb query&#8221; is still better than a &#8220;dumb query&#8221; that does full-table scans or uses a disk-temp-table.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/comment-page-1/#comment-7381</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 10 Jun 2009 22:13:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.theplanet.com/?p=1100#comment-7381</guid>
		<description>I get that this is a post about using EXPLAIN, but EXPLAIN doesn&#039;t show you that the better query would be &quot;SELECT count(*) FROM user_activity WHERE activity=&#039;Login&#039;&quot;.

Your code is cleaner and you don&#039;t waste all that network bandwidth moving useless bytes from the database to the application.

ALSO, selecting &quot;*&quot; from that table means that the query must load all the table data... if you only selected the &#039;activity&#039; column, you&#039;d find that the index itself can fulfill the entire query: the table data itself doesn&#039;t have to be consulted.

EXPLAIN can only help optimize what MySQL does with the query you give to it. If you&#039;re giving it a dumb query, it can&#039;t really help you, now can it?</description>
		<content:encoded><![CDATA[<p>I get that this is a post about using EXPLAIN, but EXPLAIN doesn&#8217;t show you that the better query would be &#8220;SELECT count(*) FROM user_activity WHERE activity=&#8217;Login&#8217;&#8221;.</p>
<p>Your code is cleaner and you don&#8217;t waste all that network bandwidth moving useless bytes from the database to the application.</p>
<p>ALSO, selecting &#8220;*&#8221; from that table means that the query must load all the table data&#8230; if you only selected the &#8216;activity&#8217; column, you&#8217;d find that the index itself can fulfill the entire query: the table data itself doesn&#8217;t have to be consulted.</p>
<p>EXPLAIN can only help optimize what MySQL does with the query you give to it. If you&#8217;re giving it a dumb query, it can&#8217;t really help you, now can it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/comment-page-1/#comment-7153</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Thu, 04 Dec 2008 18:56:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.theplanet.com/?p=1100#comment-7153</guid>
		<description>Nice post. I wasn&#039;t aware of the EXPLAIN statement, or (and I&#039;m ashamed to admit this) the benefit of adding non-primary indexes. I&#039;ll be sure to take this into consideration for my future projects. Thanks!</description>
		<content:encoded><![CDATA[<p>Nice post. I wasn&#8217;t aware of the EXPLAIN statement, or (and I&#8217;m ashamed to admit this) the benefit of adding non-primary indexes. I&#8217;ll be sure to take this into consideration for my future projects. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JeremiahX.com &#187; Blog Archive &#187; MySQL Explain Yourself!</title>
		<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/comment-page-1/#comment-7152</link>
		<dc:creator>JeremiahX.com &#187; Blog Archive &#187; MySQL Explain Yourself!</dc:creator>
		<pubDate>Thu, 04 Dec 2008 16:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.theplanet.com/?p=1100#comment-7152</guid>
		<description>[...] http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/       Read More            Post a Comment [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/" rel="nofollow">http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/</a>       Read More            Post a Comment [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AaronA</title>
		<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/comment-page-1/#comment-7146</link>
		<dc:creator>AaronA</dc:creator>
		<pubDate>Tue, 18 Nov 2008 16:27:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.theplanet.com/?p=1100#comment-7146</guid>
		<description>i had no idea you could run such a simple command to track down such a glaring inefficiency. for a little more context, is the improvement in performance very noticeable on the user side?</description>
		<content:encoded><![CDATA[<p>i had no idea you could run such a simple command to track down such a glaring inefficiency. for a little more context, is the improvement in performance very noticeable on the user side?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hazard, Web Hosting Evangelist</title>
		<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/comment-page-1/#comment-7145</link>
		<dc:creator>Kevin Hazard, Web Hosting Evangelist</dc:creator>
		<pubDate>Tue, 18 Nov 2008 16:24:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.theplanet.com/?p=1100#comment-7145</guid>
		<description>Awesome post, Matthew!</description>
		<content:encoded><![CDATA[<p>Awesome post, Matthew!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GFMorris.com &#187; links for 2008-11-15</title>
		<link>http://blog.theplanet.com/2008/11/13/mysql-explain-yourself/comment-page-1/#comment-7143</link>
		<dc:creator>GFMorris.com &#187; links for 2008-11-15</dc:creator>
		<pubDate>Sun, 16 Nov 2008 02:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.theplanet.com/?p=1100#comment-7143</guid>
		<description>[...] The Planet Blog » Blog Archive » MySQL - EXPLAIN Yourself (tags: MySQL EXPLAIN) [...]</description>
		<content:encoded><![CDATA[<p>[...] The Planet Blog » Blog Archive » MySQL &#8211; EXPLAIN Yourself (tags: MySQL EXPLAIN) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
