Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 17 Sep 2001 10:43:38 -0700
From: Aaron Bannert <aaron@clove.org>
To: dev@apr.apache.org
Subject: Re: [proposal] apr_thread_setconcurrency()
Message-ID: <20010917104338.X11014@clove.org>
References: <20010914154448.V11014@clove.org>
 <20010914154959.I12417@ebuilt.com> <20010914162151.Z11014@clove.org>
 <20010914183347.K12417@ebuilt.com> <20010915164339.H11014@clove.org>
 <20010916005510.L12417@ebuilt.com> <20010916195919.P11014@clove.org>
 <20010917092628.W11014@clove.org> <3BA6301C.5070702@pacbell.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3BA6301C.5070702@pacbell.net>;
 from bpane@pacbell.net on Mon, Sep 17, 2001 at 10:17:16AM -0700

On Mon, Sep 17, 2001 at 10:17:16AM -0700, Brian Pane wrote:
> >So that's 25 ThreadsPerChild + 3 builtin threads (door server, door
> >client, reaper) = 28, so yeah, it stabalized to the number of simultaneous
> >requests I expect to handle (aka the number of worker threads).
> >
> How were you handling 25 simultaneous requests with just
> 10 concurrent connnections in ab?

Bad wording on my part... It stabilized at the number of worker threads
being used in the system.

Since the worker queue is FIFO, all the worker threads are used fairly
soon after they enter the queue. I'll be changing this to LIFO in the
near future (per Dean's suggestion) for possible cache hits, etc...

(My poor linux box doesn't push 25 simultaneous requests very well :)

-aaron