From: Andrew Brink <abrink@ns.brink.cx>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Getting Out of Memory errors at random intervals.
Date: Sun, 13 Jan 2002 18:30:32 -0600 [thread overview]
Message-ID: <20020114003032.GA1356@ns.brink.cx> (raw)
In-Reply-To: <20020113233647.GA1198@ns.brink.cx> <E16Pugc-0008QL-00@the-village.bc.nu>
In-Reply-To: <E16Pugc-0008QL-00@the-village.bc.nu>
On Mon, Jan 14, 2002 at 12:09:14AM +0000, Alan Cox wrote:
> > On Sun, Jan 13, 2002 at 11:45:42PM +0000, Alan Cox wrote:
> > > Run something that has a sane VM in all the known awkward cases (eg the Red Hat
> > > 2.4.9 tree) and you should be just fine. If not I'd be interested to know
> >
> > I take it the vanilla 2.4.9 would also do?
>
> Nothing like it. The 2.4.9-RH tree is very different VM wise from the 2.4.9
> base tree. Linus never took the VM updates from it.
Okay. Will do.
>
> > > Andrea -aa vm patches or Rik's rmap-11b patch. Both of which seem to help
> > > no end.
> >
> > As for High loads....these boxes don't even get a load.
>
> I suspect they are - possibly only a sudden sharp burst of web traffic
> causing a lot of cgi/mysql/apache process activity.
*Shrug* I've done some experimenting with this, having a lab (30 people)
all hit the site at the same time. Holds it fine most the time. Usually
the OOM's come during the middle of the night.
>
> Alan
next prev parent reply other threads:[~2002-01-14 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 23:26 Andrew Brink
2002-01-13 23:45 ` Alan Cox
2002-01-13 23:36 ` Andrew Brink
2002-01-14 0:09 ` Alan Cox
2002-01-14 0:30 ` Andrew Brink [this message]
2002-01-14 0:44 ` Alan Cox
2002-01-14 0:39 ` Andrew Brink
2002-01-14 0:52 ` Alan Cox
2002-01-14 0:45 ` Andrew Brink
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=20020114003032.GA1356@ns.brink.cx \
--to=abrink@ns.brink.cx \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®