From: Alexander Lyamin <flx@msu.ru>
To: bzolnier@milosz.na.pl
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
zam@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: A few filesystem benchmarks w/ReiserFS4 vs Other Filesystems
Date: Fri, 3 Sep 2004 14:08:12 +0400 [thread overview]
Message-ID: <20040903100812.GA32387@alias> (raw)
In-Reply-To: <200408271745.41722.bzolnier@elka.pw.edu.pl>
Fri, Aug 27, 2004 at 05:45:41PM +0200, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
> > Execute rm -rf linux-2.6.8.1 on each file system.
> > # -------------------------------------------------------------------- #
> > ext2 | 10.26 sec @ 22% cpu
> > ext3 | 10.02 sec @ 25% cpu
> > jfs | 26.67 sec @ 27% cpu
> > rs3 | 03.22 sec @ 74% cpu
> > rs4 | 25.58 sec @ 50% cpu <- What happened to reiserfs4 here?
> > xfs | 12.51 sec @ 47% cpu
> > # -------------------------------------------------------------------- #
> > Create a 500MB file with dd to each filesystem with 1MB blocks.
> > # -------------------------------------------------------------------- #
> > ext2 | 15.72 sec @ 26% cpu
> > ext3 | 17.04 sec @ 31% cpu
> > jfs | 29.57 sec @ 25% cpu
> > rs3 | 15.21 sec @ 27% cpu
> > rs4 | 23.96 sec @ 23% cpu <- What happened to reiserfs4 here?
> > xfs | 19.07 sec @ 29% cpu
Your answers somewhere in HCH's "silent semantics" thread.
Basically reiserfs team aware that they do suck at file DELETES
and OVERWRITES. There seem to be a way to rectify this perfomance
issues in future (dynamic repacker?). Altough i was somewhat surprised
with this dd file benchmark... probably Alexander Zarochentsev knows
the answer.
--
"the liberation loophole will make it clear.."
lex lyamin
next prev parent reply other threads:[~2004-09-03 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 14:39 A few filesystem benchmarks w/ReiserFS4 vs Other Filesystems Justin Piszcz
2004-08-27 15:45 ` Bartlomiej Zolnierkiewicz
2004-09-03 10:08 ` Alexander Lyamin [this message]
2004-09-03 10:11 ` Justin Piszcz
2004-09-03 16:25 ` Hans Reiser
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=20040903100812.GA32387@alias \
--to=flx@msu.ru \
--cc=bzolnier@milosz.na.pl \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zam@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.