Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 26350 invoked by uid 6000); 6 Mar 1998 14:58:09 -0000 Received: (qmail 26343 invoked from network); 6 Mar 1998 14:58:07 -0000 Received: from localhost.hyperreal.org (HELO brianb.organic.com) (127.0.0.1) by localhost.hyperreal.org with SMTP; 6 Mar 1998 14:58:07 -0000 Message-Id: <3.0.3.32.19980306065615.0087f9e0@localhost> X-Sender: brian@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 06 Mar 1998 06:56:15 -0800 To: new-httpd@apache.org From: Brian Behlendorf Subject: Re: mmap() versus read() (fwd) In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org At 01:56 AM 3/6/98 -0800, Dean Gaudet wrote: >Everything runs on linux 2.0.x really well until you get a working set >larger than RAM. I've been thinking - would it be possible for Apache to simply not spawn more children than it had room for in RAM? It couldn't be perfect of course since there are usually other applications running on a server, but instead of having to ask the person managing the config files to guess what MaxClients should be, couldn't we automate that somehow? E.g. "MaxClients RAMLimit" :) Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- specialization is for insects brian@organic.com