Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Tue, 8 Jun 2004 18:26:16 -0400 (Eastern Daylight Time)
From: Joshua Slive <joshua@slive.ca>
To: dev@httpd.apache.org
Subject: Re: [PATCH] event driven MPM
In-Reply-To: <40C61BEC.5030009@wstoddard.com>
Message-ID: <Pine.WNT.4.58.0406081824080.2128@bronfman504>
References: <40C5CBFC.1060300@remulak.net>
 <Pine.WNT.4.60.0406081449170.2080@HEC-4949>
 <40C61BEC.5030009@wstoddard.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 8 Jun 2004, Bill Stoddard wrote:

> Joshua Slive wrote:
> > I don't have any technical comments, other than "cool".  But I can
> > confirm that many people report needing to turn KeepAlive off to get
> > reasonable performance from apache.
>
> Joshua, Tell us more. If you can't start enough processes/threads to
> handle the number of incoming connections, then setting keepalivetimeout
> from 15 to 5 seconds or turning off keepalive entirely will boost the
> apparent number of 'concurrent' connections able to be handled by the
> server. I've found this useful in several customer cases I've worked on.
> The eventdriven patch should solve this problem quite handily.

Yes, that is what I meant.  People with limited memory (so they can't
just up MaxClients) can sometimes serve many more "people" by turning off
keepalive in order to free slots.  With this patch, they should get the
best of both worlds (keepalive plus all worker threads handling actual
content).

Joshua.