Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 32918 invoked from network); 25 Mar 2008 04:49:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Mar 2008 04:49:05 -0000 Received: (qmail 82891 invoked by uid 500); 25 Mar 2008 04:48:53 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 82875 invoked by uid 500); 25 Mar 2008 04:48:53 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 82864 invoked by uid 99); 25 Mar 2008 04:48:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Mar 2008 21:48:53 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aganguly01@gmail.com designates 209.85.128.188 as permitted sender) Received: from [209.85.128.188] (HELO fk-out-0910.google.com) (209.85.128.188) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Mar 2008 04:48:14 +0000 Received: by fk-out-0910.google.com with SMTP id 26so4114337fkx.8 for ; Mon, 24 Mar 2008 21:48:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=AJw/i+pM/wrNbBmQvbN+c7sgvCB3UwEK1GeVhcUpsOo=; b=ZgF8i/Q8QPQtq8eLdkfMmlmv3x5rBqErbPb2QJbOH2k5WMh7HQVS+/8P3ffhWJRN/nAbmWB7ekECOhjoAom6mUHJ0XOjTtljWx8x19yV/+YytjqQcan9gW/opdSQo3jLYOTqicCLw+itK3rXZ13nSKcPrLbHwOL2P4iNHzzA6yU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=OWl6Rc70WaQjQ5IXYKPXLUIDo3LRI5C0n+kHqfXX343+DWOFuFEZeN4bLTP2pr6mpOuN08+rTh3jY+vQl/XFylo4rrAd4lMdQ75TvvE2aJh1ND1PSFXx5c7amBJckDStgmuzpLSl11edZ/mOGPz9YjIMRyMrx6r5q/BdiHbIErA= Received: by 10.78.139.14 with SMTP id m14mr23933819hud.40.1206420504719; Mon, 24 Mar 2008 21:48:24 -0700 (PDT) Received: by 10.78.136.18 with HTTP; Mon, 24 Mar 2008 21:48:24 -0700 (PDT) Message-ID: <2ae67e000803242148h5637d9dcqbb31935ef2b1131d@mail.gmail.com> Date: Tue, 25 Mar 2008 10:18:24 +0530 From: "Arnab Ganguly" To: users@httpd.apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10407_9472465.1206420504694" References: <2ae67e000803191411u31c4cb65g516fd3fe2920683e@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Query on Maxmemfree ------=_Part_10407_9472465.1206420504694 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > And also when > the process dies how do I make sure it releases the resource it had > acquired. >>This will happen automatically for most resources. Is there some >>particular problem you are having? Thanks for the update.My observation even after using MaxRequestPerChild param setting to non zero.What I see the process gets killed but there is no increase in free memory. Another observation is RSS size of Apache process is around 15MB but free -m gives much more resource occupied considering only Apache is running in the particular box. Regards -A On Fri, Mar 21, 2008 at 12:47 AM, Joshua Slive wrote: > On Wed, Mar 19, 2008 at 5:11 PM, Arnab Ganguly > wrote: > > Hi All, > > How do I restrain Apache process to grow to a certain limit? > > There is no function internal to apache to do that. You can probably > use ulimit in the script that starts apache. Of course, the processes > will die very ungracefully if they hit the OS limit. > > You may want to look at MaxRequestsPerChild if you have buggy/leaky > modules. > > > And also when > > the process dies how do I make sure it releases the resource it had > > acquired. > > This will happen automatically for most resources. Is there some > particular problem you are having? > > > What is the impact of the parameter MaxMemFree ? > > This won't do very much in normal use. Apache will try to free memory > back to the OS if it winds up with a bunch of unoccupied memory. The > OS may or may not reuse it. And in a busy server, it is unlikely that > particular processes will wind up allocating a bunch of memory and > then later not need it. > > Joshua. > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > ------=_Part_10407_9472465.1206420504694 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > And also when
> the process dies how do I make sure it releases the resource it had
> acquired.

>>This will happen automatically for most resources. Is there some
>>particular problem you are having?



Thanks for the update.My observation even after using MaxRequestPerChild param setting to non zero.What I see the process gets killed but there is no increase in free memory.

Another observation is RSS size of Apache process is around 15MB but free -m gives much more resource occupied considering only Apache is running in the particular box.

Regards
-A

On Fri, Mar 21, 2008 at 12:47 AM, Joshua Slive <joshua@slive.ca> wrote:
On Wed, Mar 19, 2008 at 5:11 PM, Arnab Ganguly <aganguly01@gmail.com> wrote:
> Hi All,
> How do I restrain Apache process to grow to a certain limit?

There is no function internal to apache to do that. You can probably
use ulimit in the script that starts apache. Of course, the processes
will die very ungracefully if they hit the OS limit.

You may want to look at MaxRequestsPerChild if you have buggy/leaky modules.

> And also when
> the process dies how do I make sure it releases the resource it had
> acquired.

This will happen automatically for most resources. Is there some
particular problem you are having?

> What is the impact of the parameter MaxMemFree ?

This won't do very much in normal use. Apache will try to free memory
back to the OS if it winds up with a bunch of unoccupied memory. The
OS may or may not reuse it. And in a busy server, it is unlikely that
particular processes will wind up allocating a bunch of memory and
then later not need it.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
  "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


------=_Part_10407_9472465.1206420504694--