Good news: we’ve made some improvements to our MySQL platform – and its working.
If you’ve been running a blog like this one, a CMS like Joomla, or one of the other 40+ scripts we offer in our instant-install application that uses MySQL, you’ve probably experienced some degree of slowness at least once this year.
We know it hasn’t been pretty and we apologize for that.
The first step we took in helping to accommodate the growing the demand for CGI-related service began earlier this year when upgraded the entire CGI platform with all new boxes and a new operating system. We were pretty sure this was going to solve most of the slowness complaints, but it didn’t. What it did do; however, was end an era of constant random internal server errors and give us additional flexibility in terms of what CGI-related products we might offer in the future. It was only after the CGI platform was improved upon that the issues regarding MySQL surfaced.
This was a bummer.
The first thing we tried to do was to implement a connection limitation on MySQL users.
This is a good thing because it basically protects you (or your neighbors’) scripts from going hog-wild and tying up every available MySQL connection on the server. Unfortunately, because of a limitation of MySQL 4, there was no way to effectively do that on our platform.
Alas, we set out on the task to update all 15 MySQL boxes with MySQL 5 – a version which DID allow us to put those connection limitations in place.
At the same time, we made available a new version of the MySQL hostname customers use to connect to their database. The implementation of the new load-balanced hostname format was done so that we could easily swap out servers or move around boxes without bringing customers’ sites down.
That went over quite well …
But unfortunately, customers were still complaining about their sites being slow throughout parts of the day.
An end of an era?
I’m pleased to say that I think we’ve finally pinpointed what we believe is the last in a long line of MySQL-related bottlenecks: the hard disks.
To date, we have upgraded the hard disks in 6 of the 15 MySQL boxes to a raided configuration of two 146GB 15K hard drives. And so far, it appears to be resolving the slowness issues we’ve been seeing for such a long time.
(Thanks to 67knots.com for the graph.)
Over the next couple of weeks, we hope to have all customers on servers with the updated configuration. Thanks to everyone for their ongoing patience.