From dev-return-42562-apmail-httpd-dev-archive=httpd.apache.org@httpd.apache.org Tue Jun 08 20:05:47 2004 Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 77991 invoked from network); 8 Jun 2004 20:05:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Jun 2004 20:05:46 -0000 Received: (qmail 34103 invoked by uid 500); 8 Jun 2004 20:05:56 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 33932 invoked by uid 500); 8 Jun 2004 20:05:55 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 33918 invoked by uid 99); 8 Jun 2004 20:05:54 -0000 Received: from [204.146.167.214] (HELO Boron.MeepZor.Com) (204.146.167.214) by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 08 Jun 2004 13:05:54 -0700 Received: from wstoddard.com (cpe-024-211-135-032.nc.rr.com [24.211.135.32]) by Boron.MeepZor.Com (8.11.6/8.11.6) with ESMTP id i58K5WT10869 for ; Tue, 8 Jun 2004 16:05:32 -0400 Message-ID: <40C61BEC.5030009@wstoddard.com> Date: Tue, 08 Jun 2004 16:05:00 -0400 From: Bill Stoddard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: [PATCH] event driven MPM References: <40C5CBFC.1060300@remulak.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Joshua Slive wrote: > > On Tue, 8 Jun 2004, Greg Ames wrote: > >> There are sites/workloads where keepalive timeouts tie up the majority >> of the >> active threads or processes, such as our own web site as seen at >> http://apache.org/server-status . I also see a lot of "K"s when >> running specweb99 on a stock httpd. Since we are between requests >> during keepalive waits, they can be handled differently without >> impacting a lot of code. > > > 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. Bill