good or bad?


http://members.aol.com/_ht_a/david6566//Image6.gif

A little busy.

Looks to me like mysql has gone a little crazy... you might want to restart it and see if that clears the load up a bit.

The heavy Perl load could also be connected to the mySQL load, if it is used to create mySQL connections with DBI for a forum, for example.

17 zombies is also not good so compare Top results carefully, once you've done a restart/reboot.

Lots of processes...

What are the settings in my.cnf and httpd.conf ?

It's not my server, i have a virtual account with a host i was getting ready to complain and wanted to see what you guys had to say :)

Under TIME for MySQL what does that mean? MySQL has been running for 22.6 hours or 22 min and it's using 85% of the CPU which is bad right?

Can you get the stats of the mysqld ?

Will tell you how many queries per second its receiving etc.

To get stats:

mysql -u youruser -pyourpass

Then type: status

Something like this will output.

Threads: 1 Questions: 544731 Slow queries: 0 Opens: 1874 Flush tables: 2 Open tables: 62 Queries per second avg: 0.149

Of course your need a mysql user, so if you havnt got one you wont be able to see the stats.

Originally posted by Dave22
It's not my server, i have a virtual account with a host i was getting ready to complain and wanted to see what you guys had to say :)

Under TIME for MySQL what does that mean? MySQL has been running for 22.6 hours or 22 min and it's using 85% of the CPU which is bad right?

Yes, that's what the time means. No that's not good. Hopefully they know what to do when problems like this arise :)

Can the Mysql problems be caused by too many scripts not dyeing?

I noticed that on my server caused by one script. The customer refused to do antyhing about it. So since they were a long term customer I quit complainging and edited the file to have a die function. That fixed that problem. I havent noticed any serious hanging processes since.

a script may not be freeing resources. there is quite a bit of discussion regarding this for both perl and php. google is your friend =]

For whatever reason people remember to use mysql_pconnect() and just "forget" to use mysql_close()...:angry:

I e-maled my host and they fixed it in 2 min :)

they said (we restarted the MySQL daemon and the CPU usage has gone back up. over time mysql cpu usage spikes high like you had just seen)

Whatever that means lol

Regardless of what they say it is not normal for mysql usage to be that high. Something is not right on the server. Either it is overloaded, MySQL is misconfigured, someone has some scripts which are consuming way too many resources, or something is going on.

Hopefully, for you, this doesn't happen again anytime soon. Good luck;-)

MySql is crazy here....
:D