For those that didn’t read my last post on MySQL (Its a couple of blogs down), I wrote about how we had significant problems with MySQL in general. Specifically we hated the inability to track usage by users thus allowing certain users to bring a server to it knees without being able to block and assign “blame” to the individual account that caused the problems.
While those issues are still present, we now have a patch to track that usage closely and are now creating automated tools to react in realtime to MySQL overloads and inefficient scripts that are running. So not only we will be able to block disproportionate usage by users accessing MySQL, but when our tools are done we will be able to present users with exact usage and where the problems occur on their side so that they will be able to fix/update their scripts to address these MySQL issues. In the past we knew many of the problems that happened on our servers, but we unable to react in realtime. This history helps us address repeat offenders but didn’t really do anything for the stability of our system in real time. This will soon change.
In keeping with my original promise (two blogs entries down), I have decided to make this patch public for all users of the MySQL server. If you are a hosting company and have problems with MySQL usage (I KNOW YOU DO, 100% OF YOU ) and understand the importance of individual accountability in MySQL I HIGHLY suggest you make use of this patch. If you review the patch and don’t think its worth while, then you really ought not to be doing shared hosting – I know thats harsh to say, but its true in my opinion!
Ok, enough blabbing – Below is a link to the patch – We have tested it to work with MySQL 5.0.45. If you are running a different version of the MySQL server I will at no cost create a version of the patch to work down to 5.0.37. If you are running a version of the server before that the patch may apply cleanly, but I can’t/won’t guarantee that it will work correctly. I will update the patch to ensure that it will continue to work in 5.0.x going forward from now on.
Here is the link to describe how to access and use the additional statistics that will now be available to you in the MySQL server. Please review and test carefully, as I am unwilling to provide support directly for the patch. The patch is there for you to use, but I don’t have the time or inclination to do support for something like this.
I do have high hopes for what we can accomplish with the tools that we write based on the information gathered with this patch. Although customers of Bluehost/Hostmonster won’t necessarily see or feel any difference on their end, you should notice a much more stable server experience going forward. It will most likely take us 30-45 days to roll out these changes.
For all the complaining I do about MySQL, I am actually extremely grateful to the MySQL team for creating a wonderful database that is completely free to use and provides a stellar databse for millions of people to use every day.
Matt Heaton / President Bluehost.com