MySQL Benchmarks: MySQL 5.5.11 vs Percona 5.5.10-20.1 vs MariaDB 5.2.5 – InnoDB and MyISAM
Sysbench InnoDB Read Only
Sysbench InnoDB Read/Write
Summary
Both MySQL 5.5.11 and Percona 5.5.10-20.1 showed improvements for InnoDB performance over their previous versions – MySQL 5.5.10 and Percona 5.5.8. For most folks sitting in between 16-24 cpu cores, I still think MariaDB 5.2.5 is the best choice for mixed InnoDB and MyISAM usage environments as shown in previous tests here.
- InnoDB read only results showed MySQL 5.5.11 and Percona 5.5.10-20.1 closely match each other all the way to 32 cpu threads but still both are just behind MariaDB 5.2.5 InnoDB performance. That changes at 48 and 64 cpu threads where Percona 5.5.10-20.1 jumps ahead by as much as 30-38% over MySQL 5.5.11 and 21-29% over MariaDB 5.2.5. MariaDB 5.2.5 InnoDB performance comes out on top with 20% lead at 16 cpu threads and 5% lead at 24 cpu threads.
- InnoDB read write results clearly show the benefits of Percona XtraDB InnoDB plugin utilization in both MariaDB 5.2.5 and Percona 5.5.10-20.1. At 8 and 12 cpu threads both have nearly 24% lead over MySQL 5.5.11. MySQL 5.5.11 catches up at starting at 16 cpu threads mark. Percona 5.5.10-20.1 InnoDB performance definitely improved over Percona 5.5.8 as it took over the lead from MariaDB 5.2.5 after 16 cpu threads. Percona 5.5.10-20.1 InnoDB performance had a slight dip at 32 cpu threads but jumped back up at 48 and 64 cpu threads – with a commanding 48-66% lead over MariaDB 5.2.5 and MySQL 5.5.11!
- MyISAM read only results clearly still favour MariaDB 5.2.5 up to 24 cpu threads. Cpu thread scaling still peaked at 8 cpu threads of which both MariaDB 5.2.5 and Percona 5.5.10-20.1 matched each other. MariaDB 5.2.5 MyISAM read only performance led by as much as 24% at 12 cpu threads and 40% at 16 cpu threads. At 24 cpu threads, MariaDB 5.2.5 leads Percona 5.5.10-20.1 by 5% and leads MySQL 5.5.11 by 23%.
- MyISAM read write results were pretty much all the same due to excessive table locking.
