MySQL 5.4 improves scalability

Somewhat overshadowed in last week’s headlines was news about the forthcoming MySQL 5.4 release, internally known as “Summit.” While MySQL Engineering team was somewhat heads-down last year finalizing MySQL 5.1, this new version demonstrates a dramatically shorter release cycle by focusing on just two key issues: performance and scale. Mikael Ronstrom, senior software architect, describes some of the areas of improvement in MySQL 5.4 in his blog, and you can also find benchmarks performed by Sun’s performance team. Many of these enhancements come down to MySQL’s goal to more rapidly take in community patches. As Mikael Ronstrom states in his blog:

The changes we have done in MySQL 5.4 to improve scalability and the ability to monitor the MySQL Server are:

1. Google SMP patch
2. Google IO patches
3. Update of many antiquated defaults in the MySQL Server
4. New InnoDB Thread Concurrency algorithm
5. Improved Spinloop in InnoDB mutexes and RW-locks
6. A couple of performance fixes backported from 6.0
7. Operating system specific optimisations
8. Ported the Google SMP patch to Solaris x86 and SPARC and work underway for Windows and Intel compiler as well
9. Introducing DTrace probes in the MySQL Server
10. A build script to make it easier for community to build an efficient MySQL Server based on source code

Better performance, better scale, faster incorporation of patches, and shorter release cycles — seems like a great improvement all ’round.