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 high performance environments.

Percona XtraDB includes all of InnoDB’s ACID-compliant design and advanced MVCC architecture, and adds features, more tunability, more metrics, more scalability on many cores, and better memory usage. We choose features and fixes based on customer requests and on our best judgment of real-world needs. We have not included all the InnoDB patches available. For example Google’s well-known InnoDB patch set is omitted (at least for now).

The first version of our new storage engine is 1.0.2-1, which is forked from InnoDB-plugin-1.0.2. Percona XtraDB is released under GPL v2, as is InnoDB-plugin base source code. Percona XtraDB is released only under the GPL v2 with no dual-licensing, and commercial support is available from Percona.

So what’s new in the engine? Here is a list of new features and enhancements:

INFORMATION_SCHEMA.XTRADB_ENHANCEMENTS . This table contains information about the differences between the Percona XtraDB and the same version number of standard InnoDB, so you can always learn what your engine can do. documentation

. This table contains information about the differences between the and the same version number of standard InnoDB, so you can always learn what your engine can do. documentation Improvements to SHOW INNODB STATUS . We’ve added more memory information and lock information, and fixed problems with lock information. documentation

. We’ve added more memory information and lock information, and fixed problems with lock information. documentation Improvements to InnoDB IO. Improvements of InnoDB IO subsystem, such as multiple read and write threads, read-ahead control, control io capacity and adaptive checkpointing. documentation

Improvements of InnoDB IO subsystem, such as multiple read and write threads, read-ahead control, control io capacity and adaptive checkpointing. documentation InnoDB RW-lock fixes Improvements to scalability for systems with 8+ cores. documentation

Improvements to scalability for systems with 8+ cores. documentation Buffer pool fixes Improvements of buffer_pool scalability. documentation

Improvements of buffer_pool scalability. documentation innodb_buffer_pool_pages Information about content of buffer_pool pages. documentation

Documentation is on https://www.percona.com/docs/wiki/percona-xtradb:start.

Percona XtraDB available :

* in source code from Launchpad https://launchpad.net/percona-xtradb, the version 1.0.2-1 you can get as

bzr branch lp:percona-xtradb -r tag:percona-xtradb-1.0.2-1 percona-xtradb-1.0.2-1 1 bzr branch lp : percona - xtradb - r tag : percona - xtradb - 1.0.2 - 1 percona - xtradb - 1.0.2 - 1

* as source code in tar.gz https://www.percona.com/mysql/5.1.30/source/percona-xtradb-1.0.2-1.tar.gz

* as binaries, percona xtradb is compiled in into MySQL-5.1.30 RPMS

* as separated shared library, to use as drop-in plugin for existing MySQL-5.1.30 installation https://www.percona.com/mysql/5.1.30/binary/percona-xtradb-1.0.2-1-5.1.30.x86_64.tar.gz

* OurDelta will also be using Percona XtraDB for its upcoming 5.1 builds.

XtraDB is fully compatible with existing InnoDB tables and we are going to keep compatibility in further releases.

We are open for features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans on https://bugs.launchpad.net/percona-xtradb. You can also report bugs there. Also have setup two maillists http://groups.google.com/group/percona-discussion for General discussions and http://groups.google.com/group/percona-dev for development related questions.

We are looking for 6-month release cycle of XtraDB. First several releases may come faster, as many features are planned.

Why do we say it’s a new storage engine, and not just a patchset? Because we are taking this as a serious project to evolve a new storage engine that will eventually become much more than just small variations from standard InnoDB. Percona will improve this storage engine using our own ideas, as well as incorporate improvements specifically sponsored by customers. Please contact us if you would like to sponsor any specific features. Contact form: https://www.percona.com/contacts.html