Typically, though, I wouldn't say MySQL is a CPU hog. Occasionally I've
seen it get into a weird state and it needs to be killed and brought
back up. When that happens it's a good idea to analyze your tables
before you do so to check for any errors.
-Rob
Matthew Jarvis wrote:
larry price wrote:
What is MySQL doing? Can you tell from the logs (you should be able to
turn on query logging if it's not on already)
Some versions of the mysql client do auto completion of table and
column names, and that can eat a lot of resources, but only for
interactive sessions.
I didn't view processes... I had started mySQL and then interactively
similar to:
use MyDatabase;
show tables;
describe MyTable;
describe MyOtherTable;
Matthew S. Jarvis
IT Manager
Bike Friday - "Performance that Packs."
www.bikefriday.com
541/687-0487 x140
[EMAIL PROTECTED]
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
