public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Hunter <sean@dev.sportingbet.com>
To: Adam <adam@eax.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.x series and mm
Date: Thu, 28 Jun 2001 08:33:03 +0100	[thread overview]
Message-ID: <20010628083303.A27891@dev.sportingbet.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106271008010.16671-100000@eax.student.umd.edu> <E15FI9n-0005Qz-00@the-village.bc.nu>
In-Reply-To: <E15FI9n-0005Qz-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Jun 27, 2001 at 05:27:11PM +0100

On Wed, Jun 27, 2001 at 05:27:11PM +0100, Alan Cox wrote:
> > 	I'm fairly sure it is the file buffers as the apache is already
> > 	reniced to 20, it is got max 50 processes and each of processes is
> > 	limited to like 1.5mb of size via ulimit.
> 
> nice wont help you, it controls scheduling priority. Similar a ulimit just 
> ensures that no apache process goes mad and eats lots of memory (good idea
> but not helpful here). If your working set (and thats the bit the matters)
> really is exceeding memory by a fair bit then
> 
> a)	Add more RAM - that is the real optimal approach
> b)	Make the processes smaller (eg switch to thttpd from www.acme.com)
> c)	Speed up the I/O throughput relative to CPU speed
> 	- eg the 2.2 IDE UDMA patches

It may also be worth considering 

d)	Reduce the number of Apache processes so they fit nicely in RAM

Sean

  parent reply	other threads:[~2001-06-28  7:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-27 15:08 2.2.x series and mm Adam
2001-06-27 15:20 ` Andrea Arcangeli
2001-06-27 16:27 ` Alan Cox
2001-06-27 16:39   ` Adam
2001-06-27 16:52     ` Alan Cox
2001-06-28  7:33   ` Sean Hunter [this message]
2001-06-28  9:52     ` Oliver Teuber

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=20010628083303.A27891@dev.sportingbet.com \
    --to=sean@dev.sportingbet.com \
    --cc=adam@eax.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox