I think I see the problem. Mysql really needs to be on it's own box. It's designed to just use as much power as it can find. This is a good thing for those with dedicated machines. I don't know if there's a configuration setup that tell mysql that it's not the head honcho. Does Windows have a way to start a process (mysql) in low priority?
> -----Original Message----- > From: Gary Broughton [mailto:[EMAIL PROTECTED] > Sent: Friday, August 08, 2003 4:20 AM > To: [EMAIL PROTECTED] > Subject: RE: Mysql processlist sleep time > > > The PHP one is indeed used less, probably by about 10% of the users > while it's being tested. I was simply wondering if the idle timeouts > were possibly responsible for the CPU usage problems, and I thought > (rightly or wrongly?), that setting the 'xxx_timeout' options would > close those persistent connections after the set number of seconds. > > It's just so bizarre that the mysqld program eats up all the available > CPU most of the time, inevitably almost grinding things to a > halt. I've > searched high and low for a solution, asking advice in lots of places, > tweaking loads of things here and there, and nothing seems to make any > difference whatsoever. I appreciate that Windows, MySQL and > PHP is not > really the combination of choice though! :-) > > Many thanks for your reply. > Gary > > -----Original Message----- > From: Jeremy Zawodny [mailto:[EMAIL PROTECTED] > Sent: 07 August 2003 22:55 > To: Gary Broughton > Cc: [EMAIL PROTECTED] > Subject: Re: Mysql processlist sleep time > > > On Thu, Aug 07, 2003 at 07:54:24PM +0100, Gary Broughton wrote: > > Hi all > > > > I continue to have problems with the CPU usage with MySQL and PHP > > under IIS 5 (Win2000). I recently rewrote our messageboards in PHP > > (from ASP). I now have both online separately, and if I > look at the > > processlist, the times on the ASP version rarely hit double > figures, > > but those on the PHP version often reach several hundred (wait and > > inactivity timeouts are set to 300 - I thought this would > stop it?!). > > I'm not sure what the problem is. From your description, it sounds as > if the PHP one is either used less or is more efficient about using > connections, since they're idle more often. > > > I am at a real loss as to why the processes are not being > cleared. I > > am using a persistent connection at the top of the webpage, > and every > > MySQL query is ended with a 'mysql_free_result()' > statement, including > > > before any redirects using the 'header' command. > > Hang on. You're using *persistent* connections, so why would > you expect > them not to persist? > > Jeremy > -- > Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! > <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ > > MySQL 4.0.13: up 6 days, processed 212,516,276 queries (399/sec. avg) > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
