From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rahul Karnik <rahul@genebrew.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Tracking down leaking applications
Date: Thu, 13 Apr 2006 11:30:47 +0100 [thread overview]
Message-ID: <1144924247.9989.31.camel@localhost.localdomain> (raw)
In-Reply-To: <b29067a0604090842h3bb11a88re9c175a467763c9f@mail.gmail.com>
On Sul, 2006-04-09 at 11:42 -0400, Rahul Karnik wrote:
> The process killed has been either httpd or cronolog so far. For now,
> I have upgraded to FC4's 2.6.16-1_1069 and added some swap, where
> previously there was none.
Under load apache can want a lot of memory as you have a lot of server
processes compared to say thttpd or boa.
> Is there a way to:
> - confirm that it is a userspace and not a kernel issue?
> - track down the application that is leaking memory?
Apache allows you to control the memory usage of CGIs and also the
number of servers etc. That may be a good starting point for tuning. See
the apache docs and apacheweek
prev parent reply other threads:[~2006-04-13 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 15:42 Tracking down leaking applications Rahul Karnik
2006-04-10 6:37 ` Leonid Kalev
2006-04-13 14:12 ` Rahul Karnik
2006-04-13 10:30 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1144924247.9989.31.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul@genebrew.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.