<?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: InnoDB auto-inc scalability fixed</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/</link>
	<description>Percona&#039;s MySQL &#38; InnoDB performance and scalability blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: church of default (I would also have accepted &#8220;worse is better&#8221;) &#187; Blog Archive &#187; MyISAM is better for write-heavy tables because InnoDB has a full table lock on insert.</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-626963</link>
		<dc:creator>church of default (I would also have accepted &#8220;worse is better&#8221;) &#187; Blog Archive &#187; MyISAM is better for write-heavy tables because InnoDB has a full table lock on insert.</dc:creator>
		<pubDate>Sun, 09 Aug 2009 20:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-626963</guid>
		<description>[...] supports concurrent inserts, which means you can write to a table like crazy without locking it 2.) innodb prior to 5.1.22 does not have a table lock on insert, but it does have a lock on generating the next entry for an [...]</description>
		<content:encoded><![CDATA[<p>[...] supports concurrent inserts, which means you can write to a table like crazy without locking it 2.) innodb prior to 5.1.22 does not have a table lock on insert, but it does have a lock on generating the next entry for an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ð‘Ð»Ð¾ÐºÐ¸Ñ€Ð¾Ð²Ð°Ð½Ð¸Ðµ Ñ‚Ð°Ð±Ð»Ð¸Ñ† Ð¿Ñ€Ð¸ Ð¸ÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ð¸ AUTO_INCREMENT ÑÑ‚Ð¾Ð»Ð±Ñ†Ð¾Ð² Ð² MySQL Innodb &#171; Oracle mechanics</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-596235</link>
		<dc:creator>Ð‘Ð»Ð¾ÐºÐ¸Ñ€Ð¾Ð²Ð°Ð½Ð¸Ðµ Ñ‚Ð°Ð±Ð»Ð¸Ñ† Ð¿Ñ€Ð¸ Ð¸ÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ð¸ AUTO_INCREMENT ÑÑ‚Ð¾Ð»Ð±Ñ†Ð¾Ð² Ð² MySQL Innodb &#171; Oracle mechanics</dc:creator>
		<pubDate>Fri, 26 Jun 2009 08:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-596235</guid>
		<description>[...] Ð¼Ð°ÑÑˆÑ‚Ð°Ð±Ð¸Ñ€ÑƒÐµÐ¼Ð¾ÑÑ‚Ð¸, Ð´Ð°Ð²Ð½Ð¾ ÑƒÐ¶Ðµ Ð½Ð¾Ð²Ð¾ÑÑ‚ÑŒÑŽ Ð½Ðµ ÑÐ²Ð»ÑÐµÑ‚ÑÑÂ  (ÑÐ¼. InnoDB auto-inc scalability fixed, ÑÐµÐ½Ñ‚ÑÐ±Ñ€ÑŒ 2007). ÐŸÑ€Ð°ÐºÑ‚Ð¸Ñ‡ÐµÑÐºÐ¸Ð¹ Ð¿Ñ€Ð¸Ð¼ÐµÑ€ Ñ‚Ð¸Ð¿Ð¸Ñ‡Ð½Ð¾Ð¹ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ Ð¸ [...]</description>
		<content:encoded><![CDATA[<p>[...] Ð¼Ð°ÑÑˆÑ‚Ð°Ð±Ð¸Ñ€ÑƒÐµÐ¼Ð¾ÑÑ‚Ð¸, Ð´Ð°Ð²Ð½Ð¾ ÑƒÐ¶Ðµ Ð½Ð¾Ð²Ð¾ÑÑ‚ÑŒÑŽ Ð½Ðµ ÑÐ²Ð»ÑÐµÑ‚ÑÑÂ  (ÑÐ¼. InnoDB auto-inc scalability fixed, ÑÐµÐ½Ñ‚ÑÐ±Ñ€ÑŒ 2007). ÐŸÑ€Ð°ÐºÑ‚Ð¸Ñ‡ÐµÑÐºÐ¸Ð¹ Ð¿Ñ€Ð¸Ð¼ÐµÑ€ Ñ‚Ð¸Ð¿Ð¸Ñ‡Ð½Ð¾Ð¹ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ Ð¸ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ð‘Ð»Ð¾ÐºÐ¸Ñ€Ð¾Ð²ÐºÐ¸ Ð¿Ñ€Ð¸ Ð¸ÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ð¸ AUTO_INCREMENT ÑÑ‚Ð¾Ð»Ð±Ñ†Ð¾Ð² Ð² MySQL Innodb &#171; Oracle mechanics</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-596233</link>
		<dc:creator>Ð‘Ð»Ð¾ÐºÐ¸Ñ€Ð¾Ð²ÐºÐ¸ Ð¿Ñ€Ð¸ Ð¸ÑÐ¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ð¸ AUTO_INCREMENT ÑÑ‚Ð¾Ð»Ð±Ñ†Ð¾Ð² Ð² MySQL Innodb &#171; Oracle mechanics</dc:creator>
		<pubDate>Fri, 26 Jun 2009 08:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-596233</guid>
		<description>[...] Ð¼Ð°ÑÑˆÑ‚Ð°Ð±Ð¸Ñ€ÑƒÐµÐ¼Ð¾ÑÑ‚Ð¸, Ð´Ð°Ð²Ð½Ð¾ ÑƒÐ¶Ðµ Ð½Ð¾Ð²Ð¾ÑÑ‚ÑŒÑŽ Ð½Ðµ ÑÐ²Ð»ÑÐµÑ‚ÑÑÂ  (ÑÐ¼. InnoDB auto-inc scalability fixed, ÑÐµÐ½Ñ‚ÑÐ±Ñ€ÑŒ 2007). ÐŸÑ€Ð°ÐºÑ‚Ð¸Ñ‡ÐµÑÐºÐ¸Ð¹ Ð¿Ñ€Ð¸Ð¼ÐµÑ€ Ñ‚Ð¸Ð¿Ð¸Ñ‡Ð½Ð¾Ð¹ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ Ð¸ [...]</description>
		<content:encoded><![CDATA[<p>[...] Ð¼Ð°ÑÑˆÑ‚Ð°Ð±Ð¸Ñ€ÑƒÐµÐ¼Ð¾ÑÑ‚Ð¸, Ð´Ð°Ð²Ð½Ð¾ ÑƒÐ¶Ðµ Ð½Ð¾Ð²Ð¾ÑÑ‚ÑŒÑŽ Ð½Ðµ ÑÐ²Ð»ÑÐµÑ‚ÑÑÂ  (ÑÐ¼. InnoDB auto-inc scalability fixed, ÑÐµÐ½Ñ‚ÑÐ±Ñ€ÑŒ 2007). ÐŸÑ€Ð°ÐºÑ‚Ð¸Ñ‡ÐµÑÐºÐ¸Ð¹ Ð¿Ñ€Ð¸Ð¼ÐµÑ€ Ñ‚Ð¸Ð¿Ð¸Ñ‡Ð½Ð¾Ð¹ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ñ‹ Ð¸ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hacking to make ALTER TABLE online for certain changes &#124; MySQL Performance Blog</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-182297</link>
		<dc:creator>Hacking to make ALTER TABLE online for certain changes &#124; MySQL Performance Blog</dc:creator>
		<pubDate>Mon, 29 Oct 2007 12:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-182297</guid>
		<description>[...] that more and more folks hit the InnoDB auto-inc scalability issue with MySQL 5.0 and older versions, employing other techniques to maintain the PK auto incremental [...]</description>
		<content:encoded><![CDATA[<p>[...] that more and more folks hit the InnoDB auto-inc scalability issue with MySQL 5.0 and older versions, employing other techniques to maintain the PK auto incremental [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: InnoDB ã® AUTO_INCREMENT ã¨ãƒ­ãƒƒã‚¯ - METAREAL</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-175777</link>
		<dc:creator>InnoDB ã® AUTO_INCREMENT ã¨ãƒ­ãƒƒã‚¯ - METAREAL</dc:creator>
		<pubDate>Mon, 08 Oct 2007 06:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-175777</guid>
		<description>[...] InnoDB auto-inc scalability fixed ã«ã‚ˆã‚‹ã¨æœ€æ–°ç‰ˆã® MySQL 5.1.22 [...]</description>
		<content:encoded><![CDATA[<p>[...] InnoDB auto-inc scalability fixed ã«ã‚ˆã‚‹ã¨æœ€æ–°ç‰ˆã® MySQL 5.1.22 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-174617</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Wed, 03 Oct 2007 17:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-174617</guid>
		<description>Sinisa - Which enhancements are you speaking about ?</description>
		<content:encoded><![CDATA[<p>Sinisa &#8211; Which enhancements are you speaking about ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sinisa Milivojevic</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-174613</link>
		<dc:creator>Sinisa Milivojevic</dc:creator>
		<pubDate>Wed, 03 Oct 2007 16:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-174613</guid>
		<description>A small note on the backporting of this enhancement to 5.0 and 4.1. I have spoken on the subject with Heikki couple of times, and simply put, this is not feasible. This change hardly made to 5.1. Some other nice enhancements are only in 5.2. These are, actually, quite drastic changes in the code and those are not doable in a stable release.</description>
		<content:encoded><![CDATA[<p>A small note on the backporting of this enhancement to 5.0 and 4.1. I have spoken on the subject with Heikki couple of times, and simply put, this is not feasible. This change hardly made to 5.1. Some other nice enhancements are only in 5.2. These are, actually, quite drastic changes in the code and those are not doable in a stable release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Innodb Scaling on MySQL &#171; FranÃ§ois Schiettecatte&#8217;s Blog</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-174331</link>
		<dc:creator>Innodb Scaling on MySQL &#171; FranÃ§ois Schiettecatte&#8217;s Blog</dc:creator>
		<pubDate>Tue, 02 Oct 2007 13:16:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-174331</guid>
		<description>[...] Scaling on&#160;MySQL  I have run into this bottleneck in InnoDB before and I am glad to see that it was [...]</description>
		<content:encoded><![CDATA[<p>[...] Scaling on&nbsp;MySQL  I have run into this bottleneck in InnoDB before and I am glad to see that it was [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diamond Notes &#187; Log Buffer #64: a carnival of the Vanities for DBAs</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-173302</link>
		<dc:creator>Diamond Notes &#187; Log Buffer #64: a carnival of the Vanities for DBAs</dc:creator>
		<pubDate>Fri, 28 Sep 2007 15:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-173302</guid>
		<description>[...] guys over at MySQL Performance Blog  - the high performance MySQL gurus - reported that a important bug for was fixed (currently only [...]</description>
		<content:encoded><![CDATA[<p>[...] guys over at MySQL Performance Blog  &#8211; the high performance MySQL gurus &#8211; reported that a important bug for was fixed (currently only [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/comment-page-1/#comment-173062</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Thu, 27 Sep 2007 18:13:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/09/26/innodb-auto-inc-scalability-fixed/#comment-173062</guid>
		<description>I definitely think this is one of our problems. We always seem to have contention on our database, with locked tables, and we use all innodb tables with auto increment on just about every table. I guess we&#039;ll have to start debating if we move to 5.1.x.</description>
		<content:encoded><![CDATA[<p>I definitely think this is one of our problems. We always seem to have contention on our database, with locked tables, and we use all innodb tables with auto increment on just about every table. I guess we&#8217;ll have to start debating if we move to 5.1.x.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

