One data point which is very helpful but surprisingly few people have is the history of the table sizes. Projection of data growth is very important component for capacity planning and simply watching the growth of space used on partition is not very helpful. Now as MySQL 5.0+ has information schema collecting and keeping this [...]
Shard-Query adds parallelism to queries
November 15, 2010 By 18 Comments
Preamble: On performance, workload and scalability: MySQL has always been focused on OLTP workloads. In fact, both Percona Server and MySQL 5.5.7rc have numerous performance improvements which benefit workloads that have high concurrency. Typical OLTP workloads feature numerous clients (perhaps hundreds or thousands) each reading and writing small chunks of data. The recent improvements to [...]
MySQL Limitations Part 4: One thread per connection
October 27, 2010 By 14 Comments
This is the third in a series on what’s seriously limiting MySQL in core use cases (links: part 1, 2, 3). This post is about the way MySQL handles connections, allocating one thread per connection to the server.
Estimating Replication Capacity
July 20, 2010 By 4 Comments
It is easy for MySQL replication to become bottleneck when Master server is not seriously loaded and the more cores and hard drives the get the larger the difference becomes, as long as replication remains single thread process. At the same time it is a lot easier to optimize your system when your replication runs [...]
Scaling: Consider both Size and Load
July 13, 2010 By 5 Comments
So lets imagine you have the server handling 100.000 user accounts. You can see the CPU,IO and Network usage is below 10% of capacity – does it mean you can count on server being able to handle 1.000.000 of accounts ? Not really, and there are few reasons why, I’ll name most important of them: [...]
Upgrading MySQL
January 5, 2010 By 23 Comments
Upgrading MySQL Server is a very interesting task as you can approach it with so much different “depth”. For some this is 15 minutes job for others it is many month projects. Why is that ? Performing MySQL upgrade two things should normally worry you. It is Regressions – functionality regressions when what you’ve been [...]
“Shard early, shard often”
November 16, 2009 By 6 Comments
I wrote a post a while back that said why you don’t want to shard. In that post that I tried to explain that hardware advances such as 128G of RAM being so cheap is changing the point at which you need to shard, and that the (often omitted) operational issues created by sharding can [...]
XtraDB: The Top 10 enhancements
August 13, 2009 By 5 Comments
Note: This post is part 2 of 4 on building our training workshop. Last week I talked about why you don’t want to shard. This week I’m following up with the top 10 enhancements that XtraDB has over the built-in InnoDB included in MySQL 5.0 and 5.1. Building this list was not really a scientific [...]
Why you don’t want to shard.
August 6, 2009 By 34 Comments
Note: This blog post is part 1 of 4 on building our training workshop.
The Percona training workshop will not cover sharding. If you follow our blog, you’ll notice we don’t talk much about the subject; in some cases it makes sense, but in many we’ve seen that it causes architectures to be prematurely complicated.
So let me state it: You don’t want to shard.
Optimize everything else first, and then if performance still isn’t good enough, it’s time to take a very bitter medicine. The reason you need to shard basically comes down to one of these two reasons
Percona welcomes Ryan Lowe and Vladimir Fedorkov
January 13, 2009 By 3 Comments
As we’ve said before, the Percona team just keeps growing. This time around, I’m pleased to welcome Ryan and Vladimir.
Ryan Lowe initially joined us from Florida (USA) in June. In his …a consultant, DBA (with Oracle, too!), DBA manager, and programmer makes him a great match for Percona‘s clients. He also contributed some improvements to Wordpress, and he blogs here and on Pablowe.
…and Ryan, a big welcome — we are fortunate indeed you’re working with us. And… go team!
PS: I can’t help but triple-dip, and point out that our own Ewen Fortune has …
