That's a fairly simple query you are running and should run pretty
quicker, obviously."ps auwx" isn't going to tell you enough about what
is going on to troubleshoot effectively. The cause of a slowdown on a
system is always either: CPU, Memory, I/O, or Network. "top" might be a
better choi
By the way, I tried adding "high_priority" to the SELECT statement, which
according to
http://www.mysql.com/doc/en/Internal_locking.html
gives it a higher priority, but that didn't fix the problem.
This is a desperate, devastating problem that could simply destroy our
business if we don't get it
Jackson,
Thanks for your help. Two follow-ups:
a) Is there a command to show all the table locks, or locks on a particular
table? I searched http://www.mysql.com/doc/en/index.html for locking and
locks, but I couldn't find anything.
b) I'm reading
http://www.mysql.com/doc/en/Internal_locking
This could be caused by table locking. If another Mysql process ha a lock on
the table then other processes start to queue up. Maybe this query is
getting stuck behind other queries or a single slow query.
Just a thought.
-Jackson
On Saturday 26 July 2003 11:00, Bennett Haselton wrote:
> I
I have a MySQL query running inside a CGI script on my site that, at random
intervals, seems to take 10-20 seconds to complete instead of less than 1
second. I spent so much time trying to track this down that I wrote a
script which runs once a minute on the site, which (a) captures the output
