[Sorry about the early send on the previous one ...] I just upgraded our web server from 3.23.47 to 4.02 -- and I must say that 4.02 performance rocks! :-)
I was planning to wait for the beta builds, but the thing that triggered my decision was the discovery of the query cache. Our database server (1.4 GHz Athlon on FreeBSD) typically runs between 20% and 40% load, and complex pages (like our front page!) with many queries were getting the page processing time (including the web server, a 533 MHz Alpha on NetBSD) up to 4-5 seconds. With my initial 4.02 configuration, my front page processing times are between 0.5 and 1.5 seconds -- and the database server load is hovering around 10-20%. Excellent! The query cache, though ... the documentation doesn't make many suggestions about sizing it. I started with this: set-variable = query_cache_limit=2M set-variable = query_cache_size=64M set-variable = query_cache_startup_type=1 Is this reasonable? This is what my status shows (after 30 minutes or so): | Qcache_queries_in_cache | 789 | | Qcache_inserts | 1512 | | Qcache_hits | 2847 | | Qcache_not_cached | 0 | | Qcache_free_memory | 65710008 | Is that Qcache_free_memory figure really right? And, more importantly, should I allocate more memory for this? This seems like my biggest win, and I do have 1 GB available. Tom Haapanen [EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
