From: Andrew Morton <akpm@digeo.com>
To: Hans Reiser <reiser@namesys.com>
Cc: conman@kolivas.net, linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] ext3, reiser, jfs, xfs effect on contest
Date: Fri, 31 Jan 2003 11:04:17 -0800 [thread overview]
Message-ID: <20030131110417.0b70858a.akpm@digeo.com> (raw)
In-Reply-To: <3E3A7C22.1080709@namesys.com>
Hans Reiser <reiser@namesys.com> wrote:
>
> compilation is not an effective benchmark anymore, not for Linux
> filesystems, they are all just too fast (or is it that the compilers are
> too slow?....)
>
The point of this test is to measure interactions, and fairness.
It answers the question "how much impact does heavy filesystem I/O have upon
other system activity?".
The "other system activity" in this test is a kernel compile. That is a
fairly reasonable metric, because it is sensitive to latencies in servicing
reads and it is sensitive to inappropriate page replacement decisions.
A more appropriate foreground load might be opening a word processor and
composing a short letter to Aunt Nellie, but that's harder to automate. We
expect that reduced kernel compilation time will correlate with lower-latency
letter writing.
next prev parent reply other threads:[~2003-01-31 18:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 13:20 [BENCHMARK] ext3, reiser, jfs, xfs effect on contest Con Kolivas
2003-01-31 13:37 ` Hans Reiser
2003-01-31 13:40 ` Con Kolivas
2003-01-31 13:56 ` Hans Reiser
2003-01-31 14:15 ` Con Kolivas
2003-01-31 15:21 ` Dave Jones
2003-01-31 16:40 ` Hans Reiser
2003-01-31 16:47 ` Dave Jones
2003-01-31 17:11 ` Hans Reiser
2003-01-31 19:04 ` Andrew Morton [this message]
2003-01-31 19:29 ` Hans Reiser
2003-01-31 22:21 ` Con Kolivas
2003-01-31 23:18 ` Con Kolivas
2003-02-01 0:19 ` David Lang
2003-01-31 14:09 ` Mike A. Harris
2003-01-31 14:18 ` Con Kolivas
2003-01-31 15:00 ` Maciej Soltysiak
2003-02-01 0:12 ` Con Kolivas
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=20030131110417.0b70858a.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
/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