June 20, 2013

Post: Is your MySQL buffer pool warm? Make it sweat!

… command-line option, we set the option innodb_fake_changes to prevent INSERTs, UPDATEs, and DELETEs from corrupting the data on the standby server. You will need Percona Server in order to use innodb_fake…

Post: SHOW INNODB STATUS walk through

… open inside InnoDB Main thread process no. 10099, id 88021936, state: waiting for server activity Number of rows inserted 143, updated 3000041, deleted 0, read 24865563 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00…

Post: Can Innodb Read-Ahead reduce read performance ?

… inside InnoDB Main thread process no. 3956, id 1157658976, state: sleeping Number of rows inserted 60790248, updated 11571576, deleted 0, read 63850963520 0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 24860.96…

Post: Choosing proper innodb_log_file_size

… you’re doing significant amount of writes to Innodb tables decent size of innodb_log_file_size is important for MySQL Performance… (random updates will need random IO to check if pages are up to date), number of unflushed pages in innodb buffer pool… can reduce “undo” phase is size your transactions appropriately – so updates/inserts/deletes can be sized to affect limited number of rows. Good…

Post: Statistics of InnoDB tables and indexes available in xtrabackup

…%. But it was expected, as table is really mostly inserted in, updates and deletes are rare). And let’s take index domain_id… to see how it will grow with further inserts, and I also suspect random INSERTS into so dense space going to be… post – if you are badly missing some features in MySQL, InnoDB, InnoDB-plugin, XtraDB, XtraBackup – you know whom ask for!

Post: Fix of InnoDB/XtraDB scalability of rollback segment

… about InnoDB scalability on 24-core box, and we made research of scalability problems in sysbench write workload (benchmark emulates intensive insert/delete… –oltp-order-ranges –oltp-distinct-ranges –oltp-index-updates –oltp-non-index-updates –oltp-nontrx-mode select –oltp-auto-inc off –oltp…

Post: Ultimate MySQL variable and status reference list

… Com_delete_multiblogpercona….Innodb_truncated_status_writesblogpercona.commanual innodb_use_native_aioblogpercona.commanual innodb_use_sys_mallocblogpercona.commanual innodb_versionblogpercona.commanual innodb_write_io_threadsblogpercona.commanual insert…checksblogpercona.commanual updatable_views_…

Post: InnoDB's gap locks

… FROM t WHERE i > 20 FOR UPDATE; +——+ | i | +——+ | 21 | | 25 | | 30 | +——+ transaction2> START TRANSACTION; transaction2> INSERT INTO t VALUES(26); transaction2>… SELECT. They only occur if you do UPDATE or DELETE or SELECT FOR UPDATE. InnoDB provides REPEATABLE READ for read-only SELECT,…

Post: Tuning InnoDB Concurrency Tickets

… parent(id) -> ON DELETE CASCADE -> ) ENGINE=INNODB; — 0 Tickets Used Query OK, 0 rows affected (0.00 sec) mysql> INSERT INTO parent (id…: Number of rows inserted – 1 INSERT w/FOREIGN KEY constraint: Number of rows inserted – 1 SELECT: 1 ticket per row returned UPDATE: 1 ticket per row examined + 1 ticket per row updated DELETE: 1 ticket…

Post: INSERT INTO ... SELECT Performance with Innodb tables.

Innodb would not locking rows in source table other transaction could modify the row and commit before transaction which is running INSERT…/tbl1.txt’ INTO TABLE tbl2; instead of: INSERT INTO tbl2 SELECT * from tbl1; INSERT … INTO OUTFILE does not have to set extra… look in SHOW INNODB STATUS: —TRANSACTION 0 42304626, ACTIVE 14 sec, process no 29895, OS thread id 2894768 updating or deleting mysql tables…