Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Date: Mon, 26 Jan 2004 10:09:20 -0800
From: Aaron Bannert <aaron@clove.org>
To: dev@httpd.apache.org, colm@stdlib.net
Subject: Re: [PATCH] raise MAX_SERVER_LIMIT
Message-ID: <20040126180919.GB5094@clove.org>
Mail-Followup-To: Aaron Bannert <aaron@clove.org>,
	dev@httpd.apache.org, colm@stdlib.net
References: <20040107213113.GA3595@castlerea.stdlib.net.>
 <4006B697.80707@apache.org> <20040115160438.GA19015@castlerea.stdlib.net.>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040115160438.GA19015@castlerea.stdlib.net.>
User-Agent: Mutt/1.5.4i

On Thu, Jan 15, 2004 at 04:04:38PM +0000, Colm MacCarthaigh wrote:
> There were other changes co-incidental to that, like going to 12Gb
> of RAM, which certainly helped, so it's hard to narrow it down too
> much.

Ok with 18,000 or so child processes (all in the run queue) what does
your load look like? Also, what kind of memory footprint are you seeing?

> I don't use worker because it still dumps an un-backtracable corefile
> within about 5 minutes for me. I still have no idea why, though plenty
> of corefiles. I havn't tried a serious analysis yet, becasue I've been
> moving house, but I hope to get to it soon. Moving to worker would be
> a good thing :)

I'd love to find out what's causing your worker failures. Are you using
any thread-unsafe modules or libraries?

-aaron