Not sure what is going on, but the version of MySQL you are using is
ancient. The current version of MySQL is 5.0.37. Even MySQL 4.1 (which
has been end-of-lifed) has a latest version of 4.1.22. If it is a bug
you are seeing, it likely has been fixed in a later version.
Cheers,
Jay
Kishor
Hello Everybody,
I increased the query_cache_size on one of our
main servers from 100 MB to 250 MB, since I was seeing a very high rate lot
of Qcache Low Mem prunes. The server was fine for 15 minutes and the Low mem
prunes went down to almost zero, but then started ge
[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 se
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 betwee
