June 19, 2013

Post: MySQL 5.6 Compatible Percona Toolkit 2.2 Released

…, we removed –lock-wait-timeout which set innodb_lock_wait_timeout because that now conflicts,… tools: –user, –host, –port, –password, –socket, –defaults-file. So now the command line is what … were removed, and there were several bug fixes. See https://launchpad.net/percona-toolkit/+milestone…

Post: Connecting orphaned .ibd files

… ibdata files. A well known innodb_file_per_table option brings the second one. Tables and system areas are split into different files. Usually system tablespace is located in ibdata1 file and every InnoDB table has two files e.g. actor.frm…) page 11: new style: calculated = 0x E4189B9B; recorded = 0x C168689B fixing new checksum of page 11 # # ./innochecksum -f /var/lib/mysql…

Post: XtraDB/InnoDB CPU bound benchmarks on 24cores server

… ready soon. Main difference XtraDB-rel2 it contains additional scalability fixes for buffer_pool (split_buffer_pool_mutex patch). my.cnf…=15G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=512M innodb

Post: Another scalability fix in XtraDB

fixes in InnoDB and also Google’s and your SMP fixes almost made InnoDB results acceptable in primary key lookups queries,…innodb_log_file_size=128M \ –innodb_log_files_in_group=2 \ –innodb_log_buffer_size=8M \ –innodb_flush_log_at_trx_commit=2 \ –innodb_thread_concurrency=16 \ –innodb_file

Post: DROP TABLE and stalls: Lazy Drop Table in Percona Server and the new fixes in MySQL

Suppose you have turned on innodb_file_per_table (which means that each table has its own … we are discussing here holds for when you are using innodb_file_per_table. Implementation Before going into showing how Lazy Drop… as compared to MySQL. Conclusion The new DROP TABLE related fixes in MySQL >= 5.5.23 have certainly reduced the performance…

Post: Reasons for run-away main Innodb Tablespace

So you’re running MySQL With innodb_file_per_table option but your ibdata1 file which holds main (or system) tablespace have grown… Write Buffer is fixed size (2MB = 128 of 16KB pages) and so will not affect growth of your main Innodb Tablespace. Insert… as I would like. I filed number of feature requests and I hope we’ll have a chance to fix this soon.

Post: Lost innodb tables, xfs and binary grep

… lost: MySQL had a dedicated partition on XFS file system Server was running innodb_file_per_table There was a production master and… file recovery tools for xfs – apparently they are all targeting specific file types and sure enough InnoDB is not one of the supported files…, but it really wasn’t – all of the columns were fixed size – 2bytes each, so the thing we had to look…

Post: Innodb Performance Optimization Basics

… can use noatime and nodiratime options if you’re using innodb_file_per_table and a lot of tables though benefit of… on a lot of short write transactions. innodb_thread_concurrency=8 Even with current Innodb Scalability Fixes having limited concurrency helps. The actual…. innodb_file_per_table – If you do not have too many tables use this option, so you will not have uncontrolled innodb main…

Post: Fix of InnoDB/XtraDB scalability of rollback segment

…=6G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=128M innodb

Post: What is the longest part of Innodb Recovery Process ?

… tables using innodb_file_per_table so “InnoDB: Reading tablespace information from the .ibd files…” stage was taking most of the time. Happily Innodb only… if Innodb would finally optionally store stats, same as MyISAM so one could recompute them in background. Also MySQL should fix things…