May 25, 2012

Post: InnoDB's gap locks

… > SELECT * FROM t; +——+ | age | +——+ | 21 | | 25 | | 30 | +——+ Start a transaction and delete the record …repeatable reads) so in order to prevent problems with the replication you should change…http://dev.mysql.com/doc/refman/5.1/en/innodb-locks-set.html. Conclusion MySQL uses REPEATABLE…

Post: Introducing new type of benchmark

… transactions Per Minute in tpcc-mysql). However, like Mark Callaghan mentioned…from being strict 0.5 sec, but 0.5 is the …server. For example, the famous problem with DROP TABLE performance. Does…1-8 threads): The queue piles up, waiting time grows, and the final response time grows linearly up to ~30

Comment: How to recover a single InnoDB table from a Full Backup

… similar problem and would like to recover a single table # xtrabackup_55 –backup –innodb-file-per-table –target-dir=/mnt/mysql/export…: 9 indexes have been detected. InnoDB: Progress in %: 1 2 3 4 5 6 7 8 9 10 11 12 13 14… 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40…

Post: Upgrading MySQL

… version – Upgrade of MySQL 5.0.30 to 5.0.32 is generally likely to expose less issues than 5.0.30 to 5.0.86. The… compatibility between version and so you can run MySQL 5.0 database with MySQL 5.1 with no problems in most cases. When storage type changes, such as DECIMAL field got whole another meaning in MySQL 5.0 MySQL

Post: How to debug long-running transactions in MySQL

… the processlist. The steps I use to debug this problem are as follows. First, I identify which transaction is … into a query log, and examine the log. In MySQL 5.1 and newer with the InnoDB plugin, it’s easy … session and run it in a loop with a 30-second sleep in between. Notice that it self-purges …

Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1

MySQL version We used MySQL 5.1.14-beta sources for MyISAM / InnoDB and MySQL 5.1.14-falcon bitkeeper tree bk://mysql.bkbits.net/mysql-5.1…-cache=512 –net_read_timeout=30 –net_write_timeout=30 –backlog=128 MyISAM / InnoDB:…enough. Perhaps there is still a problem with InnoDB mutexes. READ_KEY_POINT…

Post: Announcing Percona XtraDB Storage Engine: a Drop-in Replacement for Standard InnoDB

…ve added more memory information and lock information, and fixed problems with lock information. documentation Improvements to InnoDB IO. Improvements …drop-in plugin for existing MySQL-5.1.30 installation http://www.percona.com/mysql/5.1.30/binary/percona-xtradb-1.0.2-1-5.1.30.x86_64.tar.gz * …

Post: kernel_mutex problem. Or double throughput with single variable

Problem with kernel_mutex in MySQL 5.1 and MySQL 5.5 is known: Bug report. In fact in MySQL 5.6 there are some fixes that suppose to provide a solution, but MySQL 5…_spin_loops from 0 to 100 (default is 30): Threads Throughput NA 1 11178.34 2 27741.06 4 53364.52 8…

Post: MySQL 5.5.8 and Percona Server: being adaptive

MySQL 5.5.8 we have regular dips (3 times per hour) from 24900 NOTPM to 17700 NOTPM (dips of around 30…flushing of neighborhood pages (not available in MySQL 5.5.8). The problem with flushing neighborhood pages is … choice is innodb_buffer_pool_instances=1, as we implemented buffer pool scalability …

Post: MySQL - to use or not to use

…and shareholders. In reality however most of 30 year code would ether have to …problem of MySQL use is not problem of the product but problem of state of mind – you just develop applications for Oracle and MySQL…time. MySQL 5.0 with spice of enterprise features is far from being simple and MySQL 5.1+ …