{"id":836,"date":"2005-01-05T12:46:59","date_gmt":"2005-01-05T12:46:59","guid":{"rendered":"\/?p=836"},"modified":"2009-01-17T16:49:37","modified_gmt":"2009-01-17T09:49:37","slug":"mysql-tuning","status":"publish","type":"post","link":"https:\/\/harry.sufehmi.com\/archives\/2005-01-05-mysql-tuning\/","title":{"rendered":"MySQL tuning"},"content":{"rendered":"
I’ve been notified of “Too many connections” errors lately (thanks to logcheck<\/a>), and I just realized that I think I’ve missed a few emails from Yahoogroups.<\/p>\n So looking around, I found out that MySQL’s table_cache was set to 64, and max_connections at 100. While table_cache really should be (max_connections * N), where N is the max number of tables that may be in a JOIN operation at anytime. <\/p>\n No wonder that, when checked with mysqladmin -p status<\/strong>, table_cache always peaked at its maximum. table_cache has been raised to 512, and the server is running happily now.<\/p>\n For those who suspect that they need to tune their MySQL installation, here are 2 good links : Enjoy.<\/p>\n","protected":false},"excerpt":{"rendered":" I’ve been notified of “Too many connections” errors lately (thanks to logcheck), and I just realized that I think I’ve missed a few emails from Yahoogroups. So looking around, I found out that MySQL’s table_cache was set to 64, and max_connections at 100. While table_cache really should be (max_connections * N), where N is the … Continue reading MySQL tuning<\/span>
\nO-u-c-h.<\/p>\n
\n[ Tuning MySQL<\/a> ]
\n[ Tuning MySQL 4<\/a> ]<\/p>\n