exactly, NULL is a good thing. It means that php isn't constantly tearing down sessions and starting new ones. The connect process is virtually always the longest step of the query (except the big queries, but the goal is to keep them minimized in an application and use good design, indexes, etc.)
> -----Original Message----- > From: Jeremy Zawodny [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 07, 2003 5:55 PM > 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]
