Paul has been doing some testing and this patch seems to help (but not solve) the
reported
problem. The idea behind the patch is to start as many worker threads as possible on
the
first pass through the for() loop before starting the listener. Starting the listener
earlier on a loaded server w
"Bill Stoddard" <[EMAIL PROTECTED]> writes:
(I would have quoted but the text is way out at columns 89-92 or so)
I think the patch is fine, but I can't help but suspect that some of
the pain you are alleviating is caused by the known problem where the
listener thread can accept connections when
Jeff,
In my tests, this patch allows existing worker threads to continue
procesing requests while the new threads are started.
In the previous code the server would pause while new threads were
being created. The new threads started accepting work immediately,
causing the existing threads to sta
On Fri, Apr 26, 2002 at 11:32:19AM -0400, Paul J. Reder wrote:
> In my tests, this patch allows existing worker threads to continue
> procesing requests while the new threads are started.
>
> In the previous code the server would pause while new threads were
> being created. The new threads start
> On Fri, Apr 26, 2002 at 11:32:19AM -0400, Paul J. Reder wrote:
> > In my tests, this patch allows existing worker threads to continue
> > procesing requests while the new threads are started.
> >
> > In the previous code the server would pause while new threads were
> > being created. The new
PROTECTED]
> -Original Message-
> From: Bill Stoddard [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 26, 2002 11:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [PATCH] Possible fix for worker MPM performance problem
> (Updated patch)
>
>
>
>
> > On Fri, Apr 26,
I have just finished testing cvs-head against cvs-head + Bill's patch to delay listener
creation. I believe that this patch is still *very* useful and should be applied. Here
is what I did:
Started an Apache with the following config:
StartServers 1
ThreadsPerChild 64
MaxClients
