From: Will Smith <will@willsmith.org>
To: reiserfs-list@namesys.com
Subject: Benchmark : ext3 vs reiser4 and effects of fragmentation.
Date: Thu, 16 Sep 2004 06:02:54 +0800 [thread overview]
Message-ID: <4148BC0E.5010509@willsmith.org> (raw)
I've spent the last 2 days coding and running benchmarks
on the effects of fragmentation on both ext3 and
reiser4 performance.
Explanation and source code is at
http://www.willsmith.org/opensource/reiser4/fragperf/
Results and graphs are at
http://www.willsmith.org/opensource/reiser4/fragperf/test1/
Dataset is a kernel source (~200Mb) in a small 350Mb
partition, with random deletes, copies and overwrites
to cause fragmentation.
In conclusion:
1) reiser4 is slightly faster than ext3 in some cases, but
much faster in others (no surprise). However,
deletes are slightly slower.
2) ext3 degrades badly from fragmentation when running
ordered (non-random) access patterns. reiser4
also degrades but not as much.
3) the repacker can bring performance of reiser4 back
to full speed, but only if run several times.
4) the repacker is not yet stable - I had to run fsck
a few times after repacking, and once got a kernel
stack trace during repacking resulting in an
un-unmountable filesystem.
I'll gladly rerun with different parameters and/or change
the script if requested.
Will Smith
next reply other threads:[~2004-09-15 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 22:02 Will Smith [this message]
2004-09-16 8:52 ` Benchmark : ext3 vs reiser4 and effects of fragmentation Alex Zarochentsev
2004-09-16 13:08 ` mjt
2004-09-16 14:50 ` Will Smith
2004-09-16 15:03 ` mjt
2004-09-16 17:16 ` Hans Reiser
2004-09-16 15:38 ` Alex Zarochentsev
2004-09-16 15:52 ` mjt
2004-09-16 17:26 ` Hans Reiser
2004-09-16 18:38 ` Alex Zarochentsev
2004-09-16 19:00 ` mjt
2004-09-16 19:05 ` Chris Mason
2004-09-17 2:29 ` Hans Reiser
2004-09-17 17:01 ` Philippe Gramoullé
2004-09-16 15:38 ` Christian Mayrhuber
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=4148BC0E.5010509@willsmith.org \
--to=will@willsmith.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.