Comments on: InnoDB auto-inc scalability fixed

By: church of default (I would also have accepted “worse is better”) » Blog Archive » MyISAM is better for write-heavy tables because InnoDB has a full table lock on insert.

Sun, 09 Aug 2009 20:12:18 +0000

[...] 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 [...]

By: Блокирование таблиц при использовании AUTO_INCREMENT столбцов в MySQL Innodb « Oracle mechanics

Fri, 26 Jun 2009 08:27:42 +0000

[...] масштабируемости, давно уже новостью не является (см. InnoDB auto-inc scalability fixed, сентябрь 2007). Практический пример типичной проблемы и [...]

By: Блокировки при использовании AUTO_INCREMENT столбцов в MySQL Innodb « Oracle mechanics

Fri, 26 Jun 2009 08:20:23 +0000

By: Hacking to make ALTER TABLE online for certain changes | MySQL Performance Blog

Mon, 29 Oct 2007 12:49:20 +0000

[...] 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 [...]

By: InnoDB の AUTO_INCREMENT とロック - METAREAL

InnoDB の AUTO_INCREMENT とロック - METAREAL — Mon, 08 Oct 2007 06:26:59 +0000

[...] InnoDB auto-inc scalability fixed によると最新版の MySQL 5.1.22 [...]

By: peter

peter — Wed, 03 Oct 2007 17:04:37 +0000

Sinisa – Which enhancements are you speaking about ?

By: Sinisa Milivojevic

Sinisa Milivojevic — Wed, 03 Oct 2007 16:54:36 +0000

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.

By: Innodb Scaling on MySQL « François Schiettecatte’s Blog

Innodb Scaling on MySQL « François Schiettecatte’s Blog — Tue, 02 Oct 2007 13:16:32 +0000

[...] Scaling on MySQL I have run into this bottleneck in InnoDB before and I am glad to see that it was [...]

By: Diamond Notes » Log Buffer #64: a carnival of the Vanities for DBAs

Diamond Notes » Log Buffer #64: a carnival of the Vanities for DBAs — Fri, 28 Sep 2007 15:58:52 +0000

[...] guys over at MySQL Performance Blog – the high performance MySQL gurus – reported that a important bug for was fixed (currently only [...]

By: Jay

Jay — Thu, 27 Sep 2007 18:13:25 +0000

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’ll have to start debating if we move to 5.1.x.