I’ve been playing with phpMyAdmin and doing a bit of optimization of it. A few stats:
- Since I upgraded the kernel, MySQL has been up for a little under 3 days and 11 hours.
- The DB server has moved 841 MiB of traffic. This is 10 MiB an hour.
- It’s processed 131,048 queries. This is about 1,580 an hour.
- 132,000 inserted rows.
- 96K queries served out of MySQL’s query cache.
- 1,393 temporary tables created on disk to handle queries. This seems like a bottleneck, although it is only a tiny percentage.
I’ve just restarted MySQL to apply some configuration changes. (Actually, I could have changed them on the fly now that I think about it…) I tweaked the settings a bit: MySQL allows you to set limits on how much RAM it can use for various operations, and I tend to be very frugal. But I think I was shooting myself in the foot there: it was relying on disk a bit too much. It’s not like I’m running a load average of 25 and am moving gigs of traffic a day, where tuning is really vital, but it still bothers me that it’s not as efficient as it could be.
…anyone else notice that inserted rows > total queries? This seems like an error. I suppose it’s entirely possible (especially with something like an EXECUTE query), but… All that’s been going was WordPress, which does nothing but spew SELECT queries all day long.
Now I wish I hadn’t just reset the stats. 🙁