May 25, 2012

Post: InnoDB's gap locks

… SELECT * FROM t; +——+ | age | +——+ | 21 | | 25 | | 30 | +——+ Start a transaction and delete the…the performance you can disable them in two different ways: 1- …) so in order to prevent problems with the replication you ….mysql.com/doc/refman/5.1/en/innodb-locks-set.html. Conclusion MySQL

Post: Upgrading MySQL

performance regressions when performance (in a broad sense) is negatively affected. In general even minor MySQLMySQL 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: Death match! EBS versus SSD price, performance, and QoS

… sda3 32.6 1.1 0.5 2.7 0.0 0.4 54% 0 60032.9 sda3 30.0 1.0 0.5 3.0… output of iostat.) I would characterize this as very good performance. Sub-millisecond latencies to disk, pretty much consistently, for reads… write 1.4 MB/s, and we’re being stalled for a quarter of a second sometimes. This is causing acute performance problems

Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1

mysql-5.1-falcon for Falcon (Please note this is a first release of Falcon and it is still in alpha stage and performance…–table-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_NO…

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

…of other features useful in high performance environments. Percona XtraDB includes all … and lock information, and fixed problems with lock information. documentation Improvements to…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_…

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

MySQL Performance and concurrency ? The reason is – replication. In MySQL before 5.1MySQL before 5.1. In MySQL 5.1 this as well as few other problems…0 0: len 30; hex 306338386465646233353863643936633930363962373361353736383261; asc 0c88dedb358cd96c9069b73a57682a;…(truncated); 1: len 4; hex …

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…problem is really fixed. Meantime the problem with kernel_mutex is raising, I had three customer problems related to performance…0 to 100 (default is 30): Threads Throughput NA 1 11178.34 2 27741.06 4…

Post: MySQL 5.5.8 and Percona Server: being adaptive

performance, but also stable and predictable performance. I refer you to Peter’s post, PerformanceMySQL 5.5.8 we have regular dips (3 times per hour) from 24900 NOTPM to 17700 NOTPM (dips of around 30…(not available in MySQL 5.5.8). The problem with flushing…buffer_pool_instances=1, as we …

Post: Impact of the sort buffer size in MySQL

…every time it is needed. The problem with the sort buffer comes from…index: CREATE TABLE `sorttest` ( `data` char(30) DEFAULT NULL ) ENGINE=MyISAM DEFAULT …to perform 12 queries like ‘select * from sorttest order by data limit 78000,1‘ with…35 UTC 2010 i686 GNU/Linux MySQL: 5.1.41-3ubuntu12.6-log P.S.:…

Post: Interesting MySQL and PostgreSQL Benchmarks

…for this scalability problem and it is merged into MySQL 5.0.30 “Enterprise” but … Woodcrest has best performance in this test (and in many other MySQL tests), …MySQL 4.1 actually scaled pretty well with Niagra, suffering slow regression with increased concurrency rather than quick drop. In MySQL 5