Our patches for 5.0 have attracted significant interest. You can read about SecondLife’s experience here, as well as what Flickr had to say on their blog. The main improvements come in both performance gains and improvements to diagnostics (such as the improvements to the slow log output, and INDEX_STATISTICS). Despite having many requests to port [...]
Percona is hiring a Shift Support Captain
January 26, 2010 By Leave a Comment
Percona is hiring. As part of our growth process, we introduced the role of the Shift Support Captain in 2009 (see the original announcement here) to provide customers with a 24×7 technical contact person. The Shift Support Team dispatches incoming emergencies, assigns new issues, handles or escalates incoming Nagios alerts from some customers, and in [...]
Community Events February-March
January 22, 2010 By 4 Comments
February and March as busy months for Community events. There’s MySQL University, Fosdem, the Seattle MySQL Meetup & Confoo.ca.
XtraDB storage engine release 1.0.6-9
January 13, 2010 By 9 Comments
Dear Community, As of today Release 9 of XtraDB storage engine is available. The release includes following new features: The release is base on 1.0.6 version of InnoDB plugin. MySQL 5.1.42 as a base release Separate purge thread and LRU dump is implemented (this feature was actually added in Release 8, but somehow it was [...]
InnoDB, InnoDB-plugin vs XtraDB on fast storage
January 13, 2010 By 13 Comments
To continue fun with FusionIO cards, I wanted to check how MySQL / InnoDB performs here. For benchmark I took MySQL 5.1.42 with built-in InnoDB, InnoDB-plugin 1.0.6, and XtraDB 1.0.6-9 ( InnoDB with Percona patches). As benchmark engine I used tpcc-mysql with 1000 warehouses ( which gives around 90GB of data + indexes) on my [...]
Great work Innodb Team
November 30, 2009 By 8 Comments
I thought I should praise Innodb team for all the work they have been doing recently. We see a lot of cool stuff happening, especially in the area of our interest which is Performance And Scalability. Innodb Plugin 1.0.4 had a lot of great performance improvements and 1.0.5/1.0.6 gets even further with long standing caching [...]
How innodb_open_files affects performance
November 18, 2009 By 4 Comments
Recently I looked at table_cache sizing which showed larger table cache does not always provides the best performance. So I decided to look at yet another similar variable – innodb_open_files which defines how many files Innodb will keep open while working in innodb_file_per_table mode. Unlike MyISAM Innodb does not have to keep open file descriptor [...]
5.0.87-build20 Percona binaries
November 18, 2009 By 3 Comments
Dear Community, We are pleased to present the 20th build of MySQL server with Percona patches. Comparing to the previous release it has following new features: The build is based on MySQL-5.0.87 innodb_rw_lock.patch is ported from InnoDB Plugin 1.0.3 To be compatible with RedHat RPM repository, the naming scheme has changed to
1 | <rpm name>-<mysql version>-<percona build version>.<buildnumber>.<redhat version>.<architecture>.rpm |
Example:
1 | MySQL-server-percona-5.0.87-b20.29.rhel5.x86_64.rpm |
[...]
State of the art: Galera – synchronous replication for InnoDB
October 27, 2009 By 15 Comments
First time I heard about Galera on Percona Performance Conference 2009, Seppo Jaakola was presenting “Galera: Multi-Master Synchronous MySQL Replication Clusters”. It was impressed as I personally always wanted it for InnoDB, but we had it in plans at the bottom of the list, as this is very hard to implement properly. The idea by [...]
How (not) to find unused indexes
October 16, 2009 By 2 Comments
I’ve seen a few people link to an INFORMATION_SCHEMA query to be able to find any indexes that have low cardinality, in an effort to find out what indexes should be removed. This method is flawed – here’s the first reason why:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | CREATE TABLE `sales` ( `id` int(11) NOT NULL AUTO_INCREMENT, `customer_id` int(11) DEFAULT NULL, `status` enum('archived','active') DEFAULT NULL, PRIMARY KEY (`id`), KEY `status` (`status`) ) ENGINE=MyISAM AUTO_INCREMENT=65691 DEFAULT CHARSET=latin1; mysql> SELECT count(*), status FROM sales GROUP by status; +----------+---------+ | count(*) | status | +----------+---------+ |   65536 | archived | |     154 | active | +----------+---------+ 2 rows in set (0.17 sec) mysql> EXPLAIN SELECT * FROM sales WHERE status='active'; # query 1 +----+-------------+-------+------+---------------+--------+---------+-------+------+-------------+ | id | select_type | table | type | possible_keys | key   | key_len | ref  | rows | Extra      | +----+-------------+-------+------+---------------+--------+---------+-------+------+-------------+ | 1 | SIMPLE     | sales | ref | status       | status | 2      | const | 196 | Using where | +----+-------------+-------+------+---------------+--------+---------+-------+------+-------------+ 1 row in set (0.06 sec) mysql> EXPLAIN SELECT * FROM sales WHERE status='archived'; # query 2 +----+-------------+-------+------+---------------+------+---------+------+-------+-------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra      | +----+-------------+-------+------+---------------+------+---------+------+-------+-------------+ | 1 | SIMPLE     | sales | ALL | status       | NULL | NULL   | NULL | 65690 | Using where | +----+-------------+-------+------+---------------+------+---------+------+-------+-------------+ 1 row in set (0.01 sec) |
The cardinality of status index is woeful, but provided that the application [...]
