From owner-freebsd-hackers Thu Apr 3 07:26:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA27442 for hackers-outgoing; Thu, 3 Apr 1997 07:26:29 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA27437 for ; Thu, 3 Apr 1997 07:26:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id HAA03657; Thu, 3 Apr 1997 07:27:26 -0800 (PST) Message-Id: <199704031527.HAA03657@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Guido van Rooij cc: FreeBSD-hackers@freeBSD.org (FreeBSD-hackers) Subject: Re: apache like preforking apps and high loads In-reply-to: Your message of "Thu, 03 Apr 1997 15:57:08 +0200." <199704031357.PAA10893@gvr.win.tue.nl> From: David Greenman Reply-To: dg@root.com Date: Thu, 03 Apr 1997 07:27:26 -0800 Sender: owner-hackers@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk >When looking at Apacha like applications, one often sees extermely high >load averages. Apache preforks a number of processes that all block >on accept(). When a request comes in, all process are woken up and the >scheduler chooses one of the now runnable processes taht will succeed in >the accept(). The other go back to sleep. Not any more. I changed this a few days ago. Now only one process is woken up. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project