httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rajalakshmi Iyer <>
Subject Re: [users@httpd] Help needed with event MPM configuration
Date Tue, 04 Nov 2014 15:58:25 GMT
Lets say the server is running with a max of 720 connections *(*
AsyncRequestWorkerFactor* + 1) * **MaxRequestWorkers *(in this case 3 * 240
= 720)

No new connections will be accepted by the server at this point, until the
current connections is < *ThreadsPerChild +
(AsyncRequestWorkerFactor * number of idle workers)*

The server has a KeepAliveTimeout of 120 seconds. So for 2 minutes, even
though there are idle workers, the server will not be able to accept new

Is this understanding correct?


On Tue, Nov 4, 2014 at 2:48 PM, Eric Covener <> wrote:

> On Tue, Nov 4, 2014 at 9:40 AM, Rajalakshmi Iyer <>
> wrote:
> > In case of an event MPM,  unlike the worker MPM, can it be expected that
> an
> > idle worker thread starts working on a new connection or new requests on
> > another existing connection?
> >
> > Or is the worker thread tied to a connection and will only work on
> requests
> > on that connection till the connection is closed?
> Worker threads in worker are there for the life of the connection. In
> event, the thread is assigned request-by-request.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:


@BlisMedia <> <>

This email and any attachments to it may be confidential and are intended solely 
for the use of the individual to whom it is addressed. Any views or opinions 
expressed are solely those of the author and do not necessarily represent 
those of BlisMedia Ltd, a company registered in England and Wales with 
registered number 06455773. Its registered office is 3rd Floor, 101 New 
Cavendish St, London, W1W 6XH, United Kingdom.

If you are not the intended recipient of this email, you must neither take 
any action based upon its contents, nor copy or show it to anyone. Please 
contact the sender if you believe you have received this email in error. 

View raw message