…quite stable, that is why I also show 5-minute moving averages to TokuDB. So TokuDB …-table-size=10000 –mysql-user=root –oltp-tables-count=32 –mysql_table_engine=tokudb –oltp_auto_inc=on –max-time=…size = 256M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 36G innodb_log_file_size…
Post: Avoiding auto-increment holes on InnoDB with INSERT IGNORE
… using InnoDB tables on MySQL version 5.1.22 or newer? If so, you probably have gaps in your auto-increment columns. A simple… MySQL 5.1.22 InnoDB used a method to access that counter values called “Traditional”. This one uses a special table lock called AUTO-INC that remains until the end of the query or transaction. Because of this, two queries can’t have the AUTO-INC…
Post: InnoDB auto-inc scalability fixed
… customers who was affected by InnoDB auto-inc. For several of them we even advised to replace auto-inc column by that or another solution. Good news is the bug is fixed. Bad news is it is fixed only 5.1… tables with autoinc. I do not want to copy-paste MySQL documentation, the very good and informative description of the problem…
Post: Investigating MySQL Replication Latency in Percona XtraDB Cluster
… –oltp-auto-inc=off –oltp-test-mode=nontrx –oltp-nontrx-mode=update_key –mysql-user=root –mysql-password=”" –oltp-table-size=1000000 –num-threads=1…. Appendix2: Percona XtraDB Cluster related configuration # PXC Settings for Version: ‘5.5.29-55-log’ socket: ‘/var/run/mysqld/mysqld.sock’ port…
Post: Identifying the load with the help of pt-query-digest and Percona Server
…atomically, not just for new connections as in MySQL. This is very helpful for measurement as … Rows_sent: 1 Rows_examined: 655360 use test; SET timestamp=1325145746; select count(*) from auto_inc; Compare that to…SELECT wp_options # 8 0x4C16888631FD8EDB 0.1160 1.4% 5 0.0232 1.00 0.00 SELECT film # …
Post: Drilling down to the source of the problem
… famous Innodb AUTO-INC lock. That would be an easy excuse to blame everything on this lock, suggest upgrading to MySQL 5.1 and call… mostly selects which were stuck waiting. The next symptom was AUTO-INC lock which again was a false one – because single insert… the original insert is taking so long letting hundreds of AUTO-INC insert to pile up. This was also very interesting case…
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 more… auto_increment, (2) flush tables with read lock, (3) swap .frm files while keeping mysql suspended and (4) unlock the tables afterwards: — 1. mysql…; Query OK, 0 rows affected (0.00 sec) — 3. mysql> ^Z [1]+ Stopped mysql test # mv huge_table.frm huge_table_old.frm…
Comment: Percona XtraDB Cluster reference architecture with HaProxy
…mysql –mysql-engine-trx=yes –mysql-table-engine=innodb –mysql-host=haproxy –mysql-port=3307 –mysql-user=sbtest –mysql…1 pct of values are returned in 75 pct cases) Using “BEGIN” for starting transactions Using auto_inc…
Post: Fix of InnoDB/XtraDB scalability of rollback segment
… disks) to compare mysql-5.1.30-XtraDB-1.0.2-pre-release3 with default (1) and 16 rollback segments. For reference MySQL parameters: [mysqld] #mysqld…-updates –oltp-non-index-updates –oltp-nontrx-mode select –oltp-auto-inc off –oltp-connect-delay 10000 –oltp-user-delay-min 0…-ps-mode auto –mysql-host localhost –mysql-port 3306 –mysql-socket /data/vadim/benchwork/var/mysql_benchwork.sock –mysql-user user –mysql-password –mysql-db sbtest –mysql-table-engine…
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。 [...]

