It's been long known that Galera optimistic replication and enterprise-size databases are a match made in heaven. Today we're going to get a little closer to testing this statement.
A short discussion with Baron at Henrik's blog has stirred my eloquence.
Baron points to a great post by Josh Berkus where Josh contemplates the database clustering issues from a novel viewpoint. The post is really insightful. But I'm going to top that (albeit not so skilfully).
So, when I posted new benchmarks about intercontinental synchronous replication performance, I kinda was not sure if that 6000 km disaster recovery scenario was not blown out of proportions.
So, the other day I posted the performance benchmarks for the multi-master MariaDB/Galera cluster. Spectacular performance. But some of you may justifiably say:
The time has come. People keep on asking why there is a practical limit on the number of nodes in multi-master cluster and what is it exactly. So here's some no-nonsense hardcore multi-master math
This is an insert performance test implemented by running just inserts with mysqlslap against 1-3 node MySQL/Galera clusters. The results show how multi-master cluster can process more inserts than single native MySQL 5.1.38 server.
One of the pitch lines of the Drizzle project in their rewriting of MySQL code is to rely on standard libraries and make it a full blown C++ project, implying that there's no reason to hold back.
When we started Galera we explicitly decided to do it in C. We didn't have a confidence that libstdc++ was mature enough and expected to have all sorts of problems with it.
Bank restaurant that I have visited today and believe to be one of the largest restaurants (seat-wise) in Helsinki had elevated customer self-service to unparalleled (or rather super-paralleled) heights. The single mutex (cashiers) is locked only once and only to pay for food and grab fork and knife. The rest of IO (choosing and loading food) was totally asynchronous and evenly distributed between serving tables.
English
Finnish