This guide explores how to tune and optimize the MySQL Cluster database to handle diverse workload requirements. It discusses data access patterns and how to build distribution awareness into applications, before exploring schema and query optimization, tuning of parameters and how to get the best out of the latest innovations in hardware design.
The Guide concludes with recent performance benchmarks conducted with the MySQL Cluster database, an overview of how MySQL Cluster can be integrated with other MySQL storage engines, before summarizing additional resources that will enable you to optimize MySQL Cluster performance with your applications.
Download the white paper (as always, for free) from: http://www.mysql.com/why-mysql/white-papers/mysql_wp_cluster_perfomance.php
Does Sun have information regarding comparison of MySQL vs. Oracle and TimesTen DB Clustering?
Do you know of any independent evaluations that could be helpful for comparison purpose?
Hi John,
I don’t have any material comparing the products but the fundamental technology differences are:
– Oracle RAC is a shared-everything Clustering solution; the up-side is that every node in
the cluster can see all of the data which may help when you have a query that needs to
traverse all of the data. The downside is that the shared storage can be more expensive
and recovery from failures may take longer.
– MySQL Cluster is shared-nothing. The advantage is that you can scale-out with low cost
hardware and recovery from failures is extremely fast. Downsides
are that complex joins can be slow as the data is distributed amongst the data nodes.
– TimesTen is most typically used as a cache sitting between the application and an
Oracle database. TT (at least the last time I checked) doesn’t scale horizontally
Regards, Andrew.