From: rwhron@earthlink.net
To: akpm@digeo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hint benchmark reaches memory size limit on 4gb box
Date: Mon, 23 Sep 2002 19:55:58 -0400 [thread overview]
Message-ID: <20020923235558.GA28954@rushmore> (raw)
>>Should the bench be adjusted, or should I boot 2.5.36-mm1?
> Both, sorry.
Lorenzo did an update to qsbench. qsbench is much faster
than hint for a ram shortage simulation.
Current lineup:
qsbench with 2 process = 120% TotalMem
1) qsbench alone
2) qsbench with ed compile loop
3) qsbench + very small chat bench loop (5 clients, 1 room)
4) qsbench + postmark loop with ~ 40000 small files
Hm, guess i should also time 2, 3, and 4 without qsbench
for comparison. 2, 3, 4 run in less than 10 seconds
on quad xeon. The idea is to count the loops that complete
during the time for qsbench to do it's thing.
The first run on 2.5.38 got overwritten during a mkfs. :(
Any suggestions before i lose the next batch of data ;)
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2002-09-23 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 23:55 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 0:01 Hint benchmark reaches memory size limit on 4gb box rwhron
2002-09-20 0:25 ` Andrew Morton
2002-09-18 14:13 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=20020923235558.GA28954@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@digeo.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;
as well as URLs for NNTP newsgroup(s).