Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII
Date: Tue, 10 Nov 2009 22:06:28 -0800
From: Basant Kukreja <Basant.Kukreja@Sun.COM>
Subject: Re: Httpd 3.0 or something else
In-reply-to: <C71F53BA.C874D%Brian.Akins@turner.com>
Sender: Basant.Kukreja@Sun.COM
To: dev@httpd.apache.org
Message-id: <20091111060628.GA5450@lmonica2.home>
References: <6cca3db30911101056h5c5e154ag9a1f7a6891e6c81c@mail.gmail.com>
 <C71F53BA.C874D%Brian.Akins@turner.com>
User-Agent: Mutt/1.5.19 (2009-01-05)

On Tue, Nov 10, 2009 at 05:30:34PM -0500, Akins, Brian wrote:
> On 11/10/09 1:56 PM, "Greg Stein" <gstein@gmail.com> wrote:
> 
> 
> > But some buckets might be performing gzip or SSL encryption. That
> > consumes CPU within the network thread.
> 
> You could just run x times CPU cores number of "network" threads.  You can't
> use more than 100% of a CPU anyway.
> 
> The model that some of us discussed -- Greg, you may have invented it ;) --
> was to have a small pool of acceptor threads (maybe just one) and a pool of
> "worker" threads. The acceptor threads accept connections and move them into
> worker threads - that's it.  A single fd is then entirely owned by that
> worker thread until it (the fd) goes away - network/disk io, gzip, ssl, etc.
Sun Web Server (originated from Netscape) (Also Open Web Server) currently
handle this way.  It has a pool of acceptor threads which accepts connections,
acceptor threads pushes the connection to a connection queue, worker threads
pulls connection from connection queue and serves the request.  Keep alive
daemon is also multi-threaded. So multiple keep alive threads polls for the
various sets of connection for future HTTP requests.  The above architecture is
highly scalable. Recently Sun published a specweb record using this Web Server
for 128 CMT threads (32 cores system).
http://www.spec.org/web2005/results/res2009q4/web2005-20091013-00143.txt

You can see the sources from Open Web Server code if you are interested.
http://wikis.sun.com/display/wsFOSS/Open+Web+Server

Regards,
Basant.