Some Reasonable Defaults for MySQL Settings
Out of the box, MySQL isn’t exactly tuned for resilience on a busy network where things occasionally go haywire.
Sunday, November 15th, 2009
A few weeks ago we ran into another set of a problems that pointed at suboptimal default settings in MySQL. Frustrated, I realized that I had a good collection of these problems and decided to rant about them on my blog. Having had a bit of time to think about what I said and talk to some other folks about it, I feel like it’s worth expanding what I wrote and sharing it with a wider audience. Oh, you may be wondering where the third part of my CouchDB series is. A combination of things conspired against me this week, not the least of which seems to be the issue known as COUCHDB-345 in the bug tracking system used by the Apache Software Foundation. I’m still trying to work out the root of the problem(s) I’m seeing. Hopefully I will return to that soon–things were just starting to get…
Please log in to view this content.
Read More
- InnoDB Performance Monitoring with innotop
- MySQL Upgrade Testing
- Hacking with CouchDB
- An Introduction to CouchDB
- Data By The Numbers
|