From: "Phil Oester" <kernel@theoesters.com>
To: "'Stephan von Krawczynski'" <skraw@ithnet.com>
Cc: <linux-kernel@vger.kernel.org>, "'M.H.VanLeeuwen'" <vanl@megsinet.net>
Subject: RE: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
Date: Mon, 7 Jan 2002 21:11:42 -0800 [thread overview]
Message-ID: <000301c19802$f5ec5fb0$6400a8c0@philxp> (raw)
In-Reply-To: <20020107152422.42cfb554.skraw@ithnet.com>
The vmscan patch doesn't seem to help in the 'make -j' testcase.
Here's time of a couple runs:
2.4.17 vanilla
real 32m2.097s
user 9m51.800s
sys 3m47.700s
real 19m45.696s
user 9m55.820s
sys 2m32.170s
2.4.17 + vmscan patch
gave up waiting after 2 hours...never finished.
Unfortunately, box was not responsive enough to gather any useful
information. Perhaps not swapping enough???
-Phil
-----Original Message-----
From: Stephan von Krawczynski [mailto:skraw@ithnet.com]
Sent: Monday, January 07, 2002 6:24 AM
To: Phil Oester
Cc: nknight@pocketinet.com; linux-kernel@vger.kernel.org
Subject: Re: 1gb RAM + 1gb SWAP + make -j bzImage = OOM
On Sun, 6 Jan 2002 22:22:16 -0800
"Phil Oester" <kernel@theoesters.com> wrote:
> I've rerun this test a number of times, and cannot reliably reproduce
> the OOM - though it still does OOM occasionally. It never OOM's right
> after a bootup - usually the greatest chance of OOM is after 2 or 3
> consecutive runs without a reboot. Once it even froze the box and
> required a powercycle.
>
> I'm surprised you cannot OOM with 1gb RAM/256MB swap, as sometimes I'm
> over 900MB in swap - did you try consecutive runs, or just once and
then
> reboot between each run?
I tried just about everything I could think of and it never went in OOM.
Even
the first test I did were with several days uptime - meaning far away
from
"cleaning" reboot. I hate reboot :-)
> [...]
> Haven't yet tried Martin's patch - though since I can't reliably
produce
> the OOM, testing it wouldn't help much.
Well, take the other side: if you do not manage to OOM afterwards, even
at the
tenth consecutive try, there is probably something about the patch ...
Regards,
Stephan
next prev parent reply other threads:[~2002-01-08 5:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 20:32 1gb RAM + 1gb SWAP + make -j bzImage = OOM Phil Oester
2002-01-04 21:02 ` Stephan von Krawczynski
2002-01-05 0:42 ` Nicholas Knight
2002-01-05 1:24 ` Phil Oester
2002-01-05 15:17 ` Stephan von Krawczynski
2002-01-07 6:22 ` Phil Oester
2002-01-07 14:24 ` Stephan von Krawczynski
2002-01-08 5:11 ` Phil Oester [this message]
2002-01-05 21:41 ` Eric W. Biederman
2002-01-05 12:30 ` Luigi Genoni
2002-01-05 15:19 ` Stephan von Krawczynski
2002-01-05 17:57 ` Nicholas Knight
2002-01-06 14:40 ` Stephan von Krawczynski
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='000301c19802$f5ec5fb0$6400a8c0@philxp' \
--to=kernel@theoesters.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
--cc=vanl@megsinet.net \
/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