New Replication, Optimizer and High Availability features in MySQL 5.6.5!
By Rob Young on Apr 10, 2012
As the Product Manager for the MySQL database it is always great to announce when the MySQL Engineering team delivers another great product release. As a field DBA and developer it is even better when that release contains improvements and innovation that I know will help those currently using MySQL for apps that range from modest intranet sites to the most highly trafficked web sites on the web. That said, it is my pleasure to take my hat off to MySQL Engineering for today's release of the MySQL 5.6.5 Development Milestone Release ("DMR"). The new highlighted features in MySQL 5.6.5 are discussed here:
New Self-Healing Replication Clusters
The 5.6.5 DMR improves MySQL Replication by adding Global Transaction Ids and automated utilities for self-healing Replication clusters. Prior to 5.6.5 this has been somewhat of a pain point for MySQL users with most developing custom solutions or looking to costly, complex third-party solutions for these capabilities. With 5.6.5 these shackles are all but removed by a solution that is included with the GPL version of the database and supporting GPL tools.
You can learn all about the details of the great, problem solving Replication features in MySQL 5.6 in Mat Keep's Developer Zone article.
New Replication Administration and Failover Utilities
As mentioned above, the new Replication features, Global Transaction Ids specifically, are now supported by a set of automated GPL utilities that leverage the new GTIDs to provide administration and manual or auto failover to the most up to date slave (that is the default, but user configurable if needed) in the event of a master failure.
The new utilities, along with links to Engineering related blogs, are discussed in detail in the DevZone Article noted above.
Better Query Optimization and Throughput
The MySQL Optimizer team continues to amaze with the latest round of improvements in 5.6.5. Along with much refactoring of the legacy code base, the Optimizer team has improved complex query optimization and throughput by adding these functional improvements:
- Subquery Optimizations - Subqueries are now included in the Optimizer path for runtime optimization. Better throughput of nested queries enables application developers to simplify and consolidate multiple queries and result sets into a single unit or work.
- Optimizer now uses CURRENT_TIMESTAMP as default for DATETIME columns - For simplification, this eliminates the need for application developers to assign this value when a column of this type is blank by default.
- Optimizations for Range based queries - Optimizer now uses ready statistics vs Index based scans for queries with multiple range values.
- Optimizations for queries using filesort and ORDER BY. Optimization criteria/decision on execution method is done now at optimization vs parsing stage.
- Print EXPLAIN in JSON format for hierarchical readability and Enterprise tool consumption.
You can learn the details about these new features as well all of the Optimizer based improvements in MySQL 5.6 by following the Optimizer team blog.
You can download and try the MySQL 5.6.5 DMR here. (look under "Development Releases") Please let us know what you think! The new HA utilities for Replication Administration and Failover are available as part of the MySQL Workbench Community Edition, which you can download here .
Also New in MySQL Labs
As has become our tradition when announcing DMRs we also like to provide "Early Access" development features to the MySQL Community via the MySQL Labs. Today is no exception as we are also releasing the following to Labs for you to download, try and let us know your thoughts on where we need to improve:
InnoDB Online Operations
MySQL 5.6 now provides Online ADD Index, FK Drop and Online Column RENAME. These operations are non-blocking and will continue to evolve in future DMRs. You can learn the grainy details by following John Russell's blog.
InnoDB data access via Memcached API ("NotOnlySQL") - Improved refresh of an earlier feature release
Similar to Cluster 7.2, MySQL 5.6 provides direct NotOnlySQL access to InnoDB data via the familiar Memcached API. This provides the ultimate in flexibility for developers who need fast, simple key/value access and complex query support commingled within their applications.
Improved Transactional Performance, Scale
The InnoDB Engineering team has once again under promised and over delivered in the area of improved performance and scale. These improvements are also included in the aggregated Spring 2012 labs release:
InnoDB CPU cache performance improvements for modern, multi-core/CPU systems show great promise with internal tests showing:
- 2x throughput improvement for read only activity
- 6x throughput improvement for SELECT range
- Read/Write benchmarks are in progress
More details on the above are available here.
You can download all of the above in an aggregated "InnoDB 2012 Spring Labs Release" binary from the MySQL Labs. You can also learn more about these improvements and about related fixes to mysys mutex and hash sort by checking out the InnoDB team blog.
MySQL 5.6.5 is another installment in what we believe will be the best release of the MySQL database ever. It also serves as a shining example of how the MySQL Engineering team at Oracle leads in MySQL innovation.
You can get the overall Oracle message on the MySQL 5.6.5 DMR and Early Access labs features here.
As always, thanks for your continued support of MySQL, the #1 open source database on the planet!