From: Szakacsits Szabolcs <szaka@sienet.hu>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Guy <bugzilla@watkins-home.com>,
linux-fsdevel@vger.kernel.org,
'Marcel Hilzinger' <mhilzinger@linuxnewmedia.de>,
'Per Olofsson' <pelle@dsv.su.se>,
reiserfs-list@namesys.com
Subject: RE: [benchmark] seek optimization
Date: Wed, 14 Jul 2004 23:56:45 +0200 (MEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0407142307010.7492-100000@mlf.linux.rulez.org> (raw)
In-Reply-To: <OF5CD40530.F971AA8A-ON85256ED1.006E4E3B-88256ED1.006EE609@us.ibm.com>
On Wed, 14 Jul 2004, Bryan Henderson wrote:
> A simpler experiment where you copy a file from a filesystem into
> oblivion would eliminate any seeks or other delays on the write side
> and any interaction between the two and leave just the seeks on the
> read side to measure.
The intention was to point out seek elimination on the writer side ;-)
> And that information seems like it would be more useful. Many
> applications simply read and use data; they don't copy it into another
> file
Sure, and many other different kind of tests would be more useful, too.
But this experiment wasn't about those. Instead to point out, by a
relatively common tool in a common environment, that
1) The seek elimination of Reiser4 is true and quite well measurable.
Also its seek optimization is much better than any other major
filesystem's optimization on Linux.
2) Apparently the 2.6 kernel's IO scheduler has a performance problem.
Szaka
next prev parent reply other threads:[~2004-07-14 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 13:52 [benchmark] seek optimization Szakacsits Szabolcs
2004-07-14 16:33 ` Guy
2004-07-14 16:46 ` Bryan Henderson
2004-07-14 17:42 ` Szakacsits Szabolcs
2004-07-14 20:11 ` Bryan Henderson
2004-07-14 21:56 ` Szakacsits Szabolcs [this message]
2004-07-15 5:50 ` Jens Axboe
2004-07-15 10:34 ` Szakacsits Szabolcs
2004-07-15 19:17 ` Szakacsits Szabolcs
2004-07-15 19:45 ` David Masover
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.4.21.0407142307010.7492-100000@mlf.linux.rulez.org \
--to=szaka@sienet.hu \
--cc=bugzilla@watkins-home.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mhilzinger@linuxnewmedia.de \
--cc=pelle@dsv.su.se \
--cc=reiserfs-list@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;
as well as URLs for NNTP newsgroup(s).