<?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: ANALYZE:  MyISAM vs Innodb</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2008/09/03/analyze-myisam-vs-innodb/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2008/09/03/analyze-myisam-vs-innodb/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dor</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/03/analyze-myisam-vs-innodb/comment-page-1/#comment-520883</link>
		<dc:creator>Dor</dc:creator>
		<pubDate>Fri, 27 Mar 2009 12:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=485#comment-520883</guid>
		<description>Hi peter,

Each one of the queries that are displayed in this page has a specific display format which includes the query itself, the result set (neatly separated with stripped lines) &amp; the time it took to execute.

How did you do that?
I see this query-display-format in many developers websites.
It seems that you use an SQL tools for that.

Thanks in advance,
Dor.</description>
		<content:encoded><![CDATA[<p>Hi peter,</p>
<p>Each one of the queries that are displayed in this page has a specific display format which includes the query itself, the result set (neatly separated with stripped lines) &amp; the time it took to execute.</p>
<p>How did you do that?<br />
I see this query-display-format in many developers websites.<br />
It seems that you use an SQL tools for that.</p>
<p>Thanks in advance,<br />
Dor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gunnar</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/03/analyze-myisam-vs-innodb/comment-page-1/#comment-392180</link>
		<dc:creator>Gunnar</dc:creator>
		<pubDate>Wed, 26 Nov 2008 08:13:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=485#comment-392180</guid>
		<description>Hi Peter,

I fully agree with you.
I&#039;ve faced the same problem at a customer.

When the customer switched from MyISAM to InnoDb some queries that before took &gt; 1 sec now took several minutes.
The reason we slightly wrong stats in the innodb analyse which made the optimizer create tabsolutely wrong query plans.

All these queries could be fixed with manually hinting with STRAIGHT_JOIN or FORCE INDEX.

But of course it would have been much nicer if the stats would be correct on inno.

Did you file a bug for this already?</description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>I fully agree with you.<br />
I&#8217;ve faced the same problem at a customer.</p>
<p>When the customer switched from MyISAM to InnoDb some queries that before took &gt; 1 sec now took several minutes.<br />
The reason we slightly wrong stats in the innodb analyse which made the optimizer create tabsolutely wrong query plans.</p>
<p>All these queries could be fixed with manually hinting with STRAIGHT_JOIN or FORCE INDEX.</p>
<p>But of course it would have been much nicer if the stats would be correct on inno.</p>
<p>Did you file a bug for this already?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/03/analyze-myisam-vs-innodb/comment-page-1/#comment-351837</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Thu, 04 Sep 2008 17:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=485#comment-351837</guid>
		<description>StephaneC,

Well Analyze for Innodb can be helpful... It gives you cardinalities which are at least show the order of magnitude for cardinality which can help certain join queries.

The OPTIMIZE TABLE... this is good to have for Innodb in theory but in practice because this rebuilds the whole table it is most typically too slow to be useful.  There are cases when OPTIMIZE takes weeks to complete.   Plus because it builds indexes via &quot;inserts&quot; it does not really optimize things as well as it could.  And the table will be read only for the whole duration :)

MySQL 5.1 Innodb plugin can build indexes faster but you need to do particular way of dump and reload to get benefit of this fast load.</description>
		<content:encoded><![CDATA[<p>StephaneC,</p>
<p>Well Analyze for Innodb can be helpful&#8230; It gives you cardinalities which are at least show the order of magnitude for cardinality which can help certain join queries.</p>
<p>The OPTIMIZE TABLE&#8230; this is good to have for Innodb in theory but in practice because this rebuilds the whole table it is most typically too slow to be useful.  There are cases when OPTIMIZE takes weeks to complete.   Plus because it builds indexes via &#8220;inserts&#8221; it does not really optimize things as well as it could.  And the table will be read only for the whole duration <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>MySQL 5.1 Innodb plugin can build indexes faster but you need to do particular way of dump and reload to get benefit of this fast load.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StephaneC</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/03/analyze-myisam-vs-innodb/comment-page-1/#comment-351756</link>
		<dc:creator>StephaneC</dc:creator>
		<pubDate>Thu, 04 Sep 2008 08:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=485#comment-351756</guid>
		<description>So we can conclude from your tests that ANALYZE TABLE on InnoDB tables is useless. We&#039;d better only use OPTIMIZE TABLE to defragment the tables (and this will also update index statistics as OPTIMIZE is mapped to ALTER TABLE).
Am I right or can we imagine situations where ANALYZE TABLE will be helpful with InnoDB ?</description>
		<content:encoded><![CDATA[<p>So we can conclude from your tests that ANALYZE TABLE on InnoDB tables is useless. We&#8217;d better only use OPTIMIZE TABLE to defragment the tables (and this will also update index statistics as OPTIMIZE is mapped to ALTER TABLE).<br />
Am I right or can we imagine situations where ANALYZE TABLE will be helpful with InnoDB ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/03/analyze-myisam-vs-innodb/comment-page-1/#comment-351666</link>
		<dc:creator>Julien</dc:creator>
		<pubDate>Thu, 04 Sep 2008 00:13:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=485#comment-351666</guid>
		<description>Wow ! 

You&#039;ve made my day ! Thanks a lot for those informations/tests.</description>
		<content:encoded><![CDATA[<p>Wow ! </p>
<p>You&#8217;ve made my day ! Thanks a lot for those informations/tests.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
