Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <3482305AF0F6CF469ED45C0D48FAFCF705E0EC57@cnet10.cnet.com>
From: Ian Holsman <IanH@cnet.com>
To: "'new-httpd@apache.org'" <new-httpd@apache.org>
Subject: RE: Suggested direction for fixing threaded mpm thread startup.
Date: Fri, 20 Apr 2001 09:23:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"


> -----Original Message-----
> From: Bill Stoddard [mailto:bill@wstoddard.com]
> Sent: Friday, April 20, 2001 6:19 AM
> To: new-httpd@apache.org
> Subject: Re: Suggested direction for fixing threaded mpm 
> thread startup.
> 
> 
> > >
> > Beside idle_server_maintenance and MaxRequestsPerChild, are 
> there any
> > *realistic* scenarios that trigger this problem?
> >
> 
> Do large site admins run with non-zero MaxRequestsPerChild?  
> If so, then I am pretty sure this would
> be a problem for those sites that serves up content that 
> ranges from small files to huge files
> (mpegs or avis for example).  All it would take to hang up a 
> process from exiting is for someone on
> a slow link to be downloading a large file when 
> MaxRequestsPerChild is hit.
> 

we don't, (in 1.3) as we have memory leaks in some of our modules,
and the easy way was just to process a couple of reqeusts and let
the process die. we run at 512.
> 
> Bill
> 
> 
..Ian