Percona vs MySQL

Posted on

Question :

What is Percona?

How does it differ from MySQL?

When should we consider switching (or upgrading) from stock MySQL to Percona?

To add some specifics in our situation we almost exclusively use InnoDB (which I understand Percona has done a lot of optimizing for) with extensive foreign key constraints and a few stored procedures.

What we are finding at present is that MySQL is poorly optimizing our queries and so any query that goes above 3-4 joins we have to build explicitly with STRAIGHT joins to improve performance.

Answer :

Percona Server is a fork of MySQL that came into being about 7 years ago. The Percona employees are mostly former MySQL people. They care about InnoDB performance so much that they inject 30,000 lines of code into its version of MySQL to make those enhancements possible. They have been doing this since MySQL 5.0 and are still at it today.

MySQL (eh Oracle [still hate saying it]) has been trying to keep up with it Percona via its InnoDB plugin (since MySQL 5.1.38, now fully native in MySQL 5.5)

Percona once did an aggressive comparison of MySQL versions. In most cases LEFT UNCONFIGURED, older versions of MySQL outperform newer versions. You must tune MySQL to get the most of it. Switching to Percona may not get enhancements you are looking for. Even with Percona, you must find out what performance enhancements come out-of-the-box and what is settings you need to configure otherwise.

Other posts I hope you find helpful

As well as RolandoMySQLDBA’s answer, my observation is that Percona offers features that

  • come only with “paid for” stock mySQL
  • make it more that a “grown up” RDBMS


Assuming like for like performance, the extra kit from Percona makes MySQL far more viable

Leave a Reply

Your email address will not be published. Required fields are marked *