…: GTID-based replication, InnoDB Fulltext, Memcached integration, a more complete performance schema, online DDL and several other InnoDB and query optimizer … # `col2` int(11) default null # `id` int(11) not null auto_increment # To shorten this duplicate clustered index, execute: ALTER TABLE `…
Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 1, 2013 By 10 Comments
…you can, you should consider moving to InnoDB altogether. There are very few reasons…short term. Control Your Auto-Incrementing Columns PXC/Galera controls auto-incrementing values internally within the … an additional overhead, and because cluster performance is somewhat dependent on the slowest node…
Post: Avoiding auto-increment holes on InnoDB with INSERT IGNORE
November 29, 2011 By 8 Comments
…and the performance but with a small cost. Queries like INSERT … ON DUPLICATE KEY UPDATE produce gaps on the auto_increment column. To…11) NOT NULL AUTO_INCREMENT, `name` int(11) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `uniqname` (`name`) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1…
Post: Benchmarking single-row insert performance on Amazon EC2
May 16, 2012 By 17 Comments
…`) ) ENGINE=InnoDB AUTO_INCREMENT=11073789 DEFAULT CHARSET=latin1 /*!50100 PARTITION BY RANGE (transactionid) (PARTITION p0 VALUES LESS THAN (100000000) ENGINE = InnoDB, PARTITION… performance to improve, but they have an impact on the write performance. Well most of the apps rely on read performance…
Post: Extending Index for Innodb tables can hurt performance in a surprising way
May 22, 2010 By 10 Comments
… NOT NULL AUTO_INCREMENT, `a` int(11) NOT NULL, `b` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `a` (`a`) ) ENGINE=InnoDB AUTO_INCREMENT=6029313… (`id`), KEY `a` (`a`), KEY `a_2` (`a`,`b`) ) ENGINE=InnoDB AUTO_INCREMENT=6029313 DEFAULT CHARSET=latin1 mysql> select * from idxitest where a…
Post: A workaround for the performance problems of TEMPTABLE views
May 19, 2010 By 7 Comments
… filter conditions into the view query itself. This has significant performance advantages over TEMPTABLE views. A view which uses the TEMPTABLE… NULL, `c2` int(11) NOT NULL AUTO_INCREMENT, PRIMARY KEY (`c2`), KEY `c1` (`c1`) ) ENGINE=InnoDB AUTO_INCREMENT=2949071 DEFAULT CHARSET=latin1 1 row in…
Post: MySQL Users Conference - Innodb
May 9, 2007 By 6 Comments
… Improved Auto Increment handling Yet another known Innodb problem is table locks which are taken for statement duration for Inserts with auto-increment column. This…0+ Heikki also mentioned there are more things inside Innodb to unleash performance such as multiple purge threads or parallel log …
Post: Improved InnoDB fast index creation
November 6, 2011 By 4 Comments
… in the buffer pool, fast index creation provides even better performance as compared to the default method, because it does not… dump would actually make the restore slower; mysqldump –innodb-optimize-keys ignores indexes on AUTO_INCREMENT columns, because they must be indexed, so…
Post: MyISAM Scalability and Innodb, Falcon Benchmarks
October 12, 2007 By 10 Comments
…) where CREATE TABLE `t1` ( `id` int(11) unsigned NOT NULL auto_increment, `stat` int(11) unsigned NOT NULL, PRIMARY KEY (`id`), KEY… NOT NULL, PRIMARY KEY (`id`), KEY `val` (`val`) ) ENGINE=MyISAM AUTO_INCREMENT=4097 Table t1 contains about 260,000 records, all with… t1 into InnoDB, and results: Threads Queries/sec 1 296 2 341 4 544 8 493 16 498 InnoDB both performs much better…
Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1
January 8, 2007 By 117 Comments
…, auto increment primary key and couple of extra indexes. CREATE TABLE IF NOT EXISTS `$tableName` ( `id` int(10) unsigned NOT NULL auto_increment, `name… we see bad performance. We hope the performance of LIMIT queries will be fixed before release. MyISAM shows stable result. InnoDB is better…
