June 19, 2013

Post: Hacking to make ALTER TABLE online for certain changes

… hit the InnoDB auto-inc scalability issue with MySQL 5.0 and older versions, employing other techniques to maintain the PK auto incremental becomes… same layout but without auto_increment, (2) flush tables with read lock, (3) swap .frm files while keeping mysql suspended and (4… sec) mysql> INSERT INTO `huge_table` (text) VALUES (‘test’); ERROR 1062 (23000): Duplicate entry ’0′ for key 1 Unfortunately, adding auto_increment…

Comment: InnoDB auto-inc scalability fixed

…, needed. Imagine, how better the world will be if only MySQL realized the importance of back porting this quickly. James, I…. The *thing* is that auto-inc table locking issue makes InnoDB inefficient for OLTP environments where an AUTO-INC column is being used. Frank

Comment: Percona XtraDB Cluster reference architecture with HaProxy

…–test=oltp –db-driver=mysqlmysql-engine-trx=yes –mysql-table-engine=innodb –mysql-host=haproxy –mysql-port=3307 –mysql-user=sbtest –mysql-password=sbpass –oltp-table…in 75 pct cases) Using “BEGIN” for starting transactions Using auto_inc on the id column Maximum number of requests for OLTP…

Post: Fix of InnoDB/XtraDB scalability of rollback segment

… –oltp-non-index-updates –oltp-nontrx-mode select –oltp-auto-inc off –oltp-connect-delay 10000 –oltp-user-delay-min…-mode automysql-host localhost –mysql-port 3306 –mysql-socket /data/vadim/benchwork/var/mysql_benchwork.sock –mysql-user user –mysql-password –mysql-db sbtest –mysql-table…

Comment: InnoDB auto-inc scalability fixed

[...] MySQL InnoDB 的 auto-increment 會造成 INSERT 時使用 table-level lock 的 bug 終於修正 (從 2006 年一月就進 MySQL 回報系統的 bug),下個 5.1 的版本 (預定是 5.1.22) 就會包括在裡面:InnoDB auto-inc scalability fixed。 [...]

Comment: InnoDB auto-inc scalability fixed

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

Comment: MySQL Performance on Memory Appliance

… sysbench –test=oltp –mysql-table-engine=innodb –oltp-table-size=1000000 –mysql-socket=/tmp/mysql.sock –mysql-db=test –mysql-user=root –mysql-password= prepare sysbench… in 75 pct cases) Using “BEGIN” for starting transactions Using auto_inc on the id column Maximum number of requests for OLTP…

Comment: MySQL Performance on Memory Appliance

… –oltp-table-size=1000000 –db-driver=mysqlmysql-table-engine=innodb –mysql-socket=/var/lib/mysql/mysql.sock –mysql-user=root prepare sysbench –num-threads=16… in 75 pct cases) Using “BEGIN” for starting transactions Using auto_inc on the id column Maximum number of requests for OLTP…

Comment: Announcement of Percona XtraDB Cluster (alpha release)

….90 –mysql-user=root –mysql-password=rootpass –mysql-table-engine=InnoDB –mysql-engine-trx=yes –max-requests=0 –oltp-table-size=1000000 –oltp-auto-inc=off…

Comment: InnoDB auto-inc scalability fixed

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