From: Bill Davidsen <davidsen@tmr.com>
To: Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: A few thoughts on contest
Date: Sun, 22 Sep 2002 16:07:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1020922155637.7956A-100000@gatekeeper.tmr.com> (raw)
Some time ago I sent Con a set of results run on a 1GB RAM machine and
rerun on decreasing memory using mem=. The problem I noted was in the
io_half test, which runs totally in memory on a large memory machine. I
would encourage people running the test to take this into account. I now
run all my tests in no more than 256M, although runs with smaller memory
give information on which kernel might be better in those cases.
I also patched my io_XXX scripts to check the residual size of the file
and the loop count and to report the bytes transferred, seconds, and
transfer rate. This is sometimes quite different for kernels which are
otherwise very similar.
Hope this is useful to people.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
reply other threads:[~2002-09-22 20:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.3.96.1020922155637.7956A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.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).