From owner-freebsd-questions Mon Jun 5 1:14:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id ACCAF37B6A0 for ; Mon, 5 Jun 2000 01:14:24 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e558ELC08600; Mon, 5 Jun 2000 01:14:21 -0700 (PDT) Date: Mon, 5 Jun 2000 01:14:21 -0700 From: Alfred Perlstein To: Pekka.Savola@netcore.fi Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Setting restrictions on Apache processes Message-ID: <20000605011421.M17973@fw.wintelcom.net> References: <20000604234749.L17973@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from pekkas@netcore.fi on Mon, Jun 05, 2000 at 10:49:11AM +0300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Pekka Savola [000605 00:49] wrote: > > I think you'll need to fight MaxRequestsPerChild and MaxClients until > > you're able to get more ram. I'm a bit confused as to why the apache > > processes are getting so big. > > > > what are your settings for MaxRequestsPerChild and MaxClients? > > MaxRequestsPerChild was unlimited (0), MaxClients was 250; downed from 300 > and before that 500 to avoid crashy situations. > > Now I tried setting MaxReqs to 500 and upping MaxClients a bit again, to > see what happens. Actually, if it seems that apache bloats itself over time, i would lower MaxRequestsPerChild to something like 50 or 100, but it depends on how much traffic you're getting. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message