From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
To: lists@nerdbynature.de
Cc: jfs-discussion@lists.sourceforge.net,
linux-nilfs@vger.kernel.org, reiserfs-devel@vger.kernel.org,
xfs@oss.sgi.com, ext3-users@redhat.com,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: benchmark results
Date: Thu, 24 Dec 2009 21:06:45 +0900 (JST) [thread overview]
Message-ID: <20091224.210645.57462112.ryusuke@osrg.net> (raw)
In-Reply-To: <alpine.DEB.2.01.0912240205510.3483@bogon.housecafe.de>
Hi,
On Thu, 24 Dec 2009 02:31:10 -0800 (PST), Christian Kujau wrote:
> I've had the chance to use a testsystem here and couldn't resist running a
> few benchmark programs on them: bonnie++, tiobench, dbench and a few
> generic ones (cp/rm/tar/etc...) on ext{234}, btrfs, jfs, ufs, xfs, zfs.
>
> All with standard mkfs/mount options and +noatime for all of them.
>
> Here are the results, no graphs - sorry:
> http://nerdbynature.de/benchmarks/v40z/2009-12-22/
>
> Reiserfs is locking up during dbench, so I removed it from the
> config, here are some earlier results:
>
> http://nerdbynature.de/benchmarks/v40z/2009-12-21/bonnie.html
>
> Bonnie++ couldn't complete on nilfs2, only the generic tests
> and tiobench were run.
I looked at the log but couldn't identify the error.
Is that a disk full?
Thanks,
Ryusuke Konishi
> As nilfs2, ufs, zfs aren't supporting xattr, dbench
> could not be run on these filesystems.
>
> Short summary, AFAICT:
> - btrfs, ext4 are the overall winners
> - xfs to, but creating/deleting many files was *very* slow
> - if you need only fast but no cool features or journaling, ext2
> is still a good choice :)
>
> Thanks,
> Christian.
> --
> BOFH excuse #84:
>
> Someone is standing on the ethernet cable, causing a kink in the cable
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-24 12:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 10:31 benchmark results Christian Kujau
2009-12-24 12:06 ` Ryusuke Konishi [this message]
2009-12-24 12:59 ` Teran McKinney
2009-12-24 13:05 ` [Jfs-discussion] " Peter Grandi
2009-12-24 21:27 ` tytso
2009-12-24 23:46 ` Evgeniy Polyakov
2009-12-25 16:11 ` tytso
2010-01-04 16:27 ` Chris Mason
2010-01-04 18:57 ` Michael Rubin
2010-01-05 0:41 ` Dave Chinner
2010-01-05 15:31 ` Steven Pratt
2009-12-25 1:52 ` Christian Kujau
2009-12-25 13:19 ` lakshmi pathi
2009-12-25 16:14 ` tytso
2009-12-25 16:22 ` Larry McVoy
2009-12-25 16:33 ` tytso
2009-12-25 18:56 ` Christian Kujau
2009-12-25 19:32 ` Christian Kujau
2009-12-25 18:51 ` Christian Kujau
2009-12-26 16:00 ` jim owens
2009-12-26 19:06 ` Christian Kujau
2009-12-27 19:50 ` jim owens
2009-12-27 21:55 ` Christian Kujau
2009-12-27 22:33 ` tytso
2009-12-28 1:24 ` Christian Kujau
2009-12-28 14:08 ` Larry McVoy
2010-01-15 21:42 ` Edward Shishkin
2009-12-26 19:19 ` tytso
[not found] ` <AAA45328-6BEA-465C-B999-C99D45FC56FF@shobe.info>
2010-01-11 1:32 ` Larry McVoy
2009-12-25 18:42 ` Christian Kujau
2009-12-29 11:27 ` Emmanuel Florac
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=20091224.210645.57462112.ryusuke@osrg.net \
--to=konishi.ryusuke@lab.ntt.co.jp \
--cc=ext3-users@redhat.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=reiserfs-devel@vger.kernel.org \
--cc=xfs@oss.sgi.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