mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: A few filesystem benchmarks w/ReiserFS4 vs Other Filesystems
Date: Fri, 27 Aug 2004 10:39:35 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0408271037080.15499@p500> (raw)

Are balanced b-trees better for removing many files over dancing onces?
See rm -rf benchmark.

# -------------------------------------------------------------------- #
Filesystems to test:
# -------------------------------------------------------------------- #
Each file system was created with fdisk to be +1024MB.
# -------------------------------------------------------------------- #
With default initilization commands: mkfs.fs /dev/hdb[1-7]
# -------------------------------------------------------------------- #
Filesystem            Size  Used Avail Use% Mounted on
/dev/hdb1             962M   20K  913M   1% /fs/ext2
/dev/hdb2             962M   17M  897M   2% /fs/ext3
/dev/hdb3             977M   33M  945M   4% /fs/reiser3
/dev/hdb5             929M  144K  929M   1% /fs/reiser4
/dev/hdb6             973M  256K  973M   1% /fs/jfs
/dev/hdb7             973M  144K  972M   1% /fs/xfs
# -------------------------------------------------------------------- #
Untar the Linux 2.6.8.1 tarball on each file system.
# -------------------------------------------------------------------- #
ext2 | 46.88 sec @ 10% cpu
ext3 | 44.44 sec @ 12% cpu
  jfs | 57.36 sec @ 15% cpu
  rs3 | 37.03 sec @ 23% cpu
  rs4 | 27.42 sec @ 42% cpu
  xfs | 49.74 sec @ 17% cpu
# -------------------------------------------------------------------- #
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



             reply	other threads:[~2004-08-27 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 14:39 Justin Piszcz [this message]
2004-08-27 15:45 ` Bartlomiej Zolnierkiewicz
2004-09-03 10:08   ` Alexander Lyamin
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=Pine.LNX.4.61.0408271037080.15499@p500 \
    --to=jpiszcz@lucidpixels.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

all inboxes | Powered by JetHome®