<?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"
	>
<channel>
	<title>Comments on: InnoDB vs MyISAM vs Falcon benchmarks - part 1</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/</link>
	<description>Everything about MySQL Performance</description>
	<pubDate>Sun, 05 Jul 2009 01:28:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ihsan &#187; Revisi Paper Seminar</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-598728</link>
		<dc:creator>Ihsan &#187; Revisi Paper Seminar</dc:creator>
		<pubDate>Sun, 28 Jun 2009 12:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-598728</guid>
		<description>[...] - http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/ [...]</description>
		<content:encoded><![CDATA[<p>[...] - <a href="http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/" rel="nofollow">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roga&#8217;s blog &#187; MySQL 資料庫儲存引擎的選用</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-579680</link>
		<dc:creator>roga&#8217;s blog &#187; MySQL 資料庫儲存引擎的選用</dc:creator>
		<pubDate>Tue, 09 Jun 2009 07:29:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-579680</guid>
		<description>[...] 我找到一篇文章針對 MyIASM, InnoDB 和 Falcon 來做比較，在這裡面 MyIASM和 InnoDB 表現都沒有差很多，唯獨在測 READ_PK_RANGE 和 READ_KEY_POINT 時候， MyIASM 爛掉了(不過主角其實是 Falcon 因為它被打趴了)。原因是：There MyISAM shows bad scalability with increasing count of thread. I think the reason is pread system call MyISAM uses to access data and retrieving from OS cache is not scaled. InnoDB vs MyISAM vs Falcon benchmarks &#8211; part 1 [...]</description>
		<content:encoded><![CDATA[<p>[...] 我找到一篇文章針對 MyIASM, InnoDB 和 Falcon 來做比較，在這裡面 MyIASM和 InnoDB 表現都沒有差很多，唯獨在測 READ_PK_RANGE 和 READ_KEY_POINT 時候， MyIASM 爛掉了(不過主角其實是 Falcon 因為它被打趴了)。原因是：There MyISAM shows bad scalability with increasing count of thread. I think the reason is pread system call MyISAM uses to access data and retrieving from OS cache is not scaled. InnoDB vs MyISAM vs Falcon benchmarks &#8211; part 1 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: viacesi &#187; Archive du blog &#187; Donc Oracle rachète Sun !</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-552474</link>
		<dc:creator>viacesi &#187; Archive du blog &#187; Donc Oracle rachète Sun !</dc:creator>
		<pubDate>Thu, 30 Apr 2009 07:40:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-552474</guid>
		<description>[...] MySQL avait choisi Falcon, une autre technologie en vue de la sortie de la version 6. En terme de performances, Falcon est encore très loin de rivaliser avec InnoDB.Sur Java, Mark Shuttleworth ne croit pas [...]</description>
		<content:encoded><![CDATA[<p>[...] MySQL avait choisi Falcon, une autre technologie en vue de la sortie de la version 6. En terme de performances, Falcon est encore très loin de rivaliser avec InnoDB.Sur Java, Mark Shuttleworth ne croit pas [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-547242</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 23 Apr 2009 08:02:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-547242</guid>
		<description>This test is not neutral. MyISAM is disadvantaged from the beginning, since MyISAM is optimized to be used in combination with CHAR fields in contrast to VARCHAR fields. This given, MyISAM is optimized for read access when fixed row size is given.
To make a statement comparing the InnoDB and MyISAM engine the table has to be set up differently for MyISAM. Then it would be very interesting to see the results especially concerning reads for MyISAM compared to InnoDB and Falcon. Likely MyISAM will beat InnoDB is at least some of the stated queries above.</description>
		<content:encoded><![CDATA[<p>This test is not neutral. MyISAM is disadvantaged from the beginning, since MyISAM is optimized to be used in combination with CHAR fields in contrast to VARCHAR fields. This given, MyISAM is optimized for read access when fixed row size is given.<br />
To make a statement comparing the InnoDB and MyISAM engine the table has to be set up differently for MyISAM. Then it would be very interesting to see the results especially concerning reads for MyISAM compared to InnoDB and Falcon. Likely MyISAM will beat InnoDB is at least some of the stated queries above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iGuide</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-440691</link>
		<dc:creator>iGuide</dc:creator>
		<pubDate>Sat, 10 Jan 2009 05:18:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-440691</guid>
		<description>How about a speed test with a MyISAM-packed table vs InnoDB?  InnoDB's great, but if you're uploading massive tables back and forth to your server, MyISAM will be less of a hassle due to much smaller files.</description>
		<content:encoded><![CDATA[<p>How about a speed test with a MyISAM-packed table vs InnoDB?  InnoDB&#8217;s great, but if you&#8217;re uploading massive tables back and forth to your server, MyISAM will be less of a hassle due to much smaller files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dexter</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-426066</link>
		<dc:creator>Dexter</dc:creator>
		<pubDate>Sat, 27 Dec 2008 19:57:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-426066</guid>
		<description>Very intresting, i think i should migrate to InnoDB with my site's.</description>
		<content:encoded><![CDATA[<p>Very intresting, i think i should migrate to InnoDB with my site&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL: InnoDB vs MyISAM &#124; vdwaardenburg.nl</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-401653</link>
		<dc:creator>MySQL: InnoDB vs MyISAM &#124; vdwaardenburg.nl</dc:creator>
		<pubDate>Fri, 05 Dec 2008 08:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-401653</guid>
		<description>[...] used engines are InnoDB and MyISAM. But, what are the advantages of using InnoDB vs MyISAM ? InnoDB seems to be faster, but what are the advantages and disadvantages while using InnoDB or MyISAM [...]</description>
		<content:encoded><![CDATA[<p>[...] used engines are InnoDB and MyISAM. But, what are the advantages of using InnoDB vs MyISAM ? InnoDB seems to be faster, but what are the advantages and disadvantages while using InnoDB or MyISAM [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: runescape money</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-353290</link>
		<dc:creator>runescape money</dc:creator>
		<pubDate>Mon, 08 Sep 2008 09:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-353290</guid>
		<description>InnoDB tables are mostly faster than MyISAM. The only thing MyISAM supports is full-text search which is crappy and slow on large datasets anyway</description>
		<content:encoded><![CDATA[<p>InnoDB tables are mostly faster than MyISAM. The only thing MyISAM supports is full-text search which is crappy and slow on large datasets anyway</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: highscalability.com and some funny comments they make&#8230;</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-351912</link>
		<dc:creator>highscalability.com and some funny comments they make&#8230;</dc:creator>
		<pubDate>Thu, 04 Sep 2008 21:46:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-351912</guid>
		<description>[...] InnoDB tables are mostly faster than MyISAM. The only thing MyISAM supports is full-text search which is crappy and slow on large datasets anyway. [...]</description>
		<content:encoded><![CDATA[<p>[...] InnoDB tables are mostly faster than MyISAM. The only thing MyISAM supports is full-text search which is crappy and slow on large datasets anyway. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: itix</title>
		<link>http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-348235</link>
		<dc:creator>itix</dc:creator>
		<pubDate>Sun, 24 Aug 2008 05:27:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/#comment-348235</guid>
		<description>Once we query the log table we read over the logs. Our table handler did very well with it. For each thread we performed the warm-up run (duration 180 sec), and then ran three effective runs (duration of each is 60 sec). Only problem our final result was much different.</description>
		<content:encoded><![CDATA[<p>Once we query the log table we read over the logs. Our table handler did very well with it. For each thread we performed the warm-up run (duration 180 sec), and then ran three effective runs (duration of each is 60 sec). Only problem our final result was much different.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
