From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Subject: Re: oom running aim7 on 2.5.61-mm1
Date: Thu, 20 Feb 2003 09:07:15 -0500 [thread overview]
Message-ID: <20030220140715.GA6851@rushmore> (raw)
> This test creates memory pressure, but shouldn't OOM:
2.5.62-mm1 ran AIM7 compute and other tests without OOM.
> I'll try 2.5.61-mm1 with elevator=cfq.
I ran 2.5.61-mm1 with both default and cfq I/O elevators.
These results could be skewed by the mm_struct leak in 61-mm1,
but FWIW:
Default 2.5.61-mm1 I/O scheduler did better in most cases:
AIM7 dbase test:
load jobs/minute (higher is better)
2.5.61-mm1 8 76.6
2.5.61-mm1-cfq 8 68.7
2.5.61-mm1-cfq 16 100.0
2.5.61-mm1 16 132.4
2.5.61-mm1-cfq 32 136.5
2.5.61-mm1 32 198.7
AIM7 fileserver test
load jobs/minute (higher is better)
2.5.61-mm1-cfq 10 149.8
2.5.61-mm1 10 175.3
Tiobench ext sequential reads
threads MB/sec CPU usage max latency
2.5.61-mm1-cfq 16 9.34 14.06% 497.8 (seconds)
2.5.61-mm1 16 15.52 53.86% 5.2
More quad xeon benchmarks at:
http://home.earthlink.net/~rwhron/kernel/bigbox.html
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2003-02-20 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 14:07 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 23:01 oom running aim7 on 2.5.61-mm1 rwhron
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=20030220140715.GA6851@rushmore \
--to=rwhron@earthlink.net \
--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