Percona Server version 5.1.52-12.3 is now available for download. The main purpose of this release is to update the current Percona release candidate to the latest version of MySQL 5.1. The release also includes the HandlerSocket plugin, which provides NoSQL features in Percona Server. Functionality Added or Changed Percona Server 5.1.52-12.3 is now based on [...]
XtraDB: The Top 10 enhancements
Note: This post is part 2 of 4 on building our training workshop. Last week I talked about why you don’t want to shard. This week I’m following up with the top 10 enhancements that XtraDB has over the built-in InnoDB included in MySQL 5.0 and 5.1. Building this list was not really a scientific [...]
Announcing Percona XtraDB Storage Engine: a Drop-in Replacement for Standard InnoDB
Today we officially announce our new storage engine, “Percona XtraDB“, which is based on the InnoDB storage engine. It’s 100% backwards-compatible with standard InnoDB, so you can use it as a drop-in replacement in your current environment. It is designed to scale better on modern hardware, and includes a variety of other features useful in [...]
How Percona does a MySQL Performance Audit
Our customers or prospective customers often ask us how we do a performance audit (it’s our most popular service). I thought I should write a blog post that will both answer their question, so I can just reply “read all about it at this URL” and share our methodology with readers a little bit. This [...]
More patches
After some pause we are going to announce bunch of patches we made and ported for last period. Ported patches (ported from Google V2 patch): – innodb_fsync_source.patch – Show information about callers of fsync, more info – innodb_io_tune.patch – Port of two patches InnodbIOTune and InnodbAsync, more info – innodb_extra_status.patch – Show more information about [...]
A quest for the full InnoDB status
When running InnoDB you are able to dig into the engine internals, look at various gauges and counters, see past deadlocks and the list of all open transactions. This is in your reach with one simple command —
1 | SHOW ENGINE InnoDB STATUS |
. On most occasions it works beautifully. The problems appear when you have a large spike in [...]

