From owner-freebsd-questions Sun Jun 4 23:47:56 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 3777337B597 for ; Sun, 4 Jun 2000 23:47:53 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e556lo306453; Sun, 4 Jun 2000 23:47:50 -0700 (PDT) Date: Sun, 4 Jun 2000 23:47:50 -0700 From: Alfred Perlstein To: Pekka.Savola@netcore.fi Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Setting restrictions on Apache processes Message-ID: <20000604234749.L17973@fw.wintelcom.net> References: <20000604220826.K17973@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 08:26:41AM +0300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Pekka Savola [000604 22:26] wrote: > > > I'm having trouble with 3.4-STABLE and Apache 1.3.12 w/ PHP3 and MySQL. > > > > A solution that may help is lowering the value that apache uses for > > "max serving" (MaxRequestsPerChild) to something lower than you have > > it at now, this will get the apache processes to exit more often which > > can cause more load, but hopefully the ones that are eating reasources > > will die and let fresh ones with less memory leaked back in. > > This is a very good idea, I'll try it. > > Also, for the record, what seems to happen is swap size growing too much, > obtaining the "critical mass". With 128 MB of memory, everything looks > clean with 220 MB of swap, but just wait for it to get to 300 MB.. In > 'top', every second process is swapping () and those degenerated, > resource chomping processes start to appear. It seems there is no other > way than to add more RAM. 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? are you using any special modules? mod_perl? php? mod_perl is known to explode the httpd to 20 megabytes, if possible you may want to run a dedicated mod_perl server on a different IP. The best solution is getting that ram in asap. -- -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