From owner-freebsd-hackers  Thu Aug 30 10:21: 7 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7])
	by hub.freebsd.org (Postfix) with ESMTP id 93C0A37B40C
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 30 Aug 2001 10:21:03 -0700 (PDT)
	(envelope-from tinguely@web.cs.ndsu.nodak.edu)
Received: (from tinguely@localhost)
	by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f7UHJtR51738;
	Thu, 30 Aug 2001 12:19:55 -0500 (CDT)
	(envelope-from tinguely)
Date: Thu, 30 Aug 2001 12:19:55 -0500 (CDT)
From: mark tinguely <tinguely@web.cs.ndsu.nodak.edu>
Message-Id: <200108301719.f7UHJtR51738@web.cs.ndsu.nodak.edu>
To: dphoenix@bravenet.com, tinguely@web.cs.ndsu.nodak.edu
Subject: Re: memory + apache
Cc: freebsd-hackers@FreeBSD.ORG
In-Reply-To: <20010830085917.I98751-100000@gandalf.bravenet.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hackers.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hackers>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hackers>
X-Loop: FreeBSD.ORG


>  Yeah that is what I am thinking to. My guess is some large array allocated
>  in the php code maybe or a sql query taking to long to finish eating up
>  all the ram. That is kind of interesting to know.

you said that the CPU usage spikes also at the time of the memory depletion?
I wonder if you have some fork storm. If you had process accounting
enabled and match it up with the web log file and vmstat activity you
may be able to narrow your search.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message