<?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: Leveraging the InnoDB Plugin</title>
	<atom:link href="http://ronaldbradford.com/blog/leveraging-the-innodb-plugin-2011-02-11/feed/" rel="self" type="application/rss+xml" />
	<link>http://ronaldbradford.com/blog/leveraging-the-innodb-plugin-2011-02-11/</link>
	<description>Expert times and information on MySQL</description>
	<lastBuildDate>Thu, 09 May 2013 15:50:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: LinuxJedi</title>
		<link>http://ronaldbradford.com/blog/leveraging-the-innodb-plugin-2011-02-11/comment-page-1/#comment-11074</link>
		<dc:creator>LinuxJedi</dc:creator>
		<pubDate>Mon, 14 Feb 2011 10:29:37 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=3468#comment-11074</guid>
		<description>It should probably be noted that in tests with InnoDB 1.1.4 for both Drizzle and MySQL 5.5 we have found that innodb_file_per_table leads to around a 15% performance hit on read/write OLTP Sysbench.  We are guessing that this is due to the extra fsyncs required for the common tablespace as well as the tablespace-per-table files but we haven&#039;t looked too deeply into it yet.</description>
		<content:encoded><![CDATA[<p>It should probably be noted that in tests with InnoDB 1.1.4 for both Drizzle and MySQL 5.5 we have found that innodb_file_per_table leads to around a 15% performance hit on read/write OLTP Sysbench.  We are guessing that this is due to the extra fsyncs required for the common tablespace as well as the tablespace-per-table files but we haven&#8217;t looked too deeply into it yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holger Thiel</title>
		<link>http://ronaldbradford.com/blog/leveraging-the-innodb-plugin-2011-02-11/comment-page-1/#comment-11072</link>
		<dc:creator>Holger Thiel</dc:creator>
		<pubDate>Mon, 14 Feb 2011 10:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=3468#comment-11072</guid>
		<description>This is not a migration issue.

The innodb_file_per_table is stable since MySQL 5.0.

You can use the same InnoDB tables/files from MySQL 5.1 in MySQL 5.5.

Beware: To many tables are not good with using innodb_file_per_table.</description>
		<content:encoded><![CDATA[<p>This is not a migration issue.</p>
<p>The innodb_file_per_table is stable since MySQL 5.0.</p>
<p>You can use the same InnoDB tables/files from MySQL 5.1 in MySQL 5.5.</p>
<p>Beware: To many tables are not good with using innodb_file_per_table.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniël van Eeden</title>
		<link>http://ronaldbradford.com/blog/leveraging-the-innodb-plugin-2011-02-11/comment-page-1/#comment-11063</link>
		<dc:creator>Daniël van Eeden</dc:creator>
		<pubDate>Sun, 13 Feb 2011 11:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://ronaldbradford.com/blog/?p=3468#comment-11063</guid>
		<description>This could also be a nice moment to recreate the InnoDB logfiles and adjust the size of them. The parameters are innodb_log_file_size and innodb_log and innodb_log_files_in_group. I believe that the default is 2 files of 5MB, which is very small. Changing this to 2 files of 1G could improve performance.</description>
		<content:encoded><![CDATA[<p>This could also be a nice moment to recreate the InnoDB logfiles and adjust the size of them. The parameters are innodb_log_file_size and innodb_log and innodb_log_files_in_group. I believe that the default is 2 files of 5MB, which is very small. Changing this to 2 files of 1G could improve performance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
