We run a site with c.20-60 users on at any one time, usually about 15 will be authenticated users posting in the forums.
With page caching switched on, the cache table generates a lot of overhead, then crashes.
This can be fixed by either:
1. restarting mysql
2. restarting the server
3. uninstalling and reinstalling mysql due to unresolvable (for me at least) .sock errors.
Obviously this isn't ideal, and I'd like to work out a way to fix it properly. I've turned page caching off, but oddly my cache table after truncation is still growing to about 20mb in a 240mb or so database very quickly, and still generates overhead. I run repair on it every so often (also get quite a bit of overhead on sessions and watchdog as well), but at the moment am doing it manually since I'd rather not set up a cron to do it (have to learn how first anyway!) if I can fix it properly instead.
Using apache2/php5/mysql5 - vps hosting, 256mb ram, Drupal 4.7.3
Been reading through the following threads and the linked mailing list discussion and wondering if this is related: http://drupal.org/node/43336
http://drupal.org/node/42817
The questions I want to ask are these:
1. Is this a bug or an issue with myisam tables?
2. Is there something in my my.cnf I ought to be tweaking?
I've seen posts elsewhere about duplicate key errors, we've had those as well but I don't think that's the issue here since I understand those are only generated by page caching?