Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 71318 invoked from network); 1 Sep 2008 07:29:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Sep 2008 07:29:06 -0000 Received: (qmail 36701 invoked by uid 500); 1 Sep 2008 07:29:01 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 36324 invoked by uid 500); 1 Sep 2008 07:28:59 -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: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 36313 invoked by uid 99); 1 Sep 2008 07:28:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 00:28:59 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.202.165.36] (HELO smtpauth20.prod.mesa1.secureserver.net) (64.202.165.36) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 01 Sep 2008 07:27:59 +0000 Received: (qmail 30009 invoked from network); 1 Sep 2008 07:28:27 -0000 Received: from unknown (98.212.183.150) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 01 Sep 2008 07:28:26 -0000 Message-ID: <48BB9999.20100@rowe-clan.net> Date: Mon, 01 Sep 2008 02:28:25 -0500 From: "William A. Rowe, Jr." User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: [community] 2.3.0 alpha on October 1? References: <48AE1049.1080309@rowe-clan.net> <52D3BF705D654A2195DA3328384007F2@bspc0> In-Reply-To: <52D3BF705D654A2195DA3328384007F2@bspc0> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Bing Swen wrote: > > Although Apache is famous for its modular design and configuration > flexibility, it seems > these new comers are challenging the relevance of Apache in real use. Is > there any > chance for Apache to get much better performance while retaining its design > beauty? No, and yes. No, there's very little chance that anyone will randomly attack the poor perfomance before 2.3.0 alpha, and the rule of open source software is that the one with an itch to scratch is the one who will author and offer the patch. Maybe that's you :) And yes, httpd quite possibly approaches their performance if you drop off 3/4 of all of the default modules. Especially if it's tuned to use the event mpm and sendfile. And finally, yes; httpd 2.4/3.0 is likely to offer (not "always" use, some modules will be foreever incompatible) a truly async mode of operation. That is, with the current enhanced poll semantics (about 5 different flavors across 4 major OS's) there's no reason not to park workers with "nothing to do right now" away from any worker thread. But I'd challenge you to configure nothing but the bare minimum modules which solve your configuration and *then* post some notes about performance. If you are comparing an "everything plus the kitchen sink" default Apache httpd to a far more featureless server, there's really nothing we can tell you other than the features suck CPU. Bill