I can't really say I've ever had an issue with MySQL eating up a bunch of CPU time. I would check to see what your cache hit ratio is. Are you going to disk for stuff that should be in memory. Do you have any memory allocated for MySQL to suck up when it starts up a database? Do you have binary logging turned on?
Miller On 8/16/06, Matthew Jarvis <[EMAIL PROTECTED]> wrote:
Ben Barrett wrote: > Agreed, it was likely rebuilding table indexes and/or verifying data... > depending on the system it is running on, the disk might be held up on > other tasks. Well, what it's doing in the background just sitting there at a prompt overnight I can't really say... maybe it's inclined to do stuff like this... > I'm guessing you're not running on linux, since you mentioned coldfusion :) > Sounds like the "residual" system load was higher than during normal > mySQL usage; if you do happen to be on linux check out vmstat. > Yes - Linux (slackware). Will take a look at vmstat - thanks. > How big is the DB? Can it fit in memory? (make sure you have good UPS > if so!) DB isn't terribly large - I don't have the #'s handy though... > > In regards, to the subject line, I also wanted to round this discussion > out by daying, "NO", IMO :) > MySQL has been improving over the years in terms of its own efficiency, > and the bottom line is that CPU time is continually cheaper ;) Okay... Thanks, Matt 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
