On Apr 4, 2005 5:59 AM, Chris Hammond chris@tac.esi.net wrote:
It works just fine with 4.0.24 so I has something to do with 4.1.x. I am sure it is not a "problem" with MySQL but something in my setup. The thing is, a simple default install is quick with 4.0.x but with my machine, which is a Sun dual Opteron box running CentOS 4 x86_64, is just dog slow. Of course I will want to get 4.1.x running, but I may have to come back to it.
At the time, there was nothing but MySQL running on the server, all unused services were shut off. The cpu was barely being touched.
As you said, it would be worthwhile to capture the output of top. I like to use
# date >> /tmp/topper.txt; top -b -n 1 >> /tmp/topper.txt
You will get the top output in that text file - it can be useful to tweak other things in root's toprc prior to doing this (like hiding zombie processes). If I'm having weird problems like this on a box I frequently put that top command into a cron that runs every 5 or 10 minutes and you can see what's going on with the box.
Greg