From: Keith Mannthey <kmannth@us.ibm.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Benchmarking data from a raid machine 2.6.34-rc3
Date: Fri, 23 Apr 2010 17:06:18 -0700 [thread overview]
Message-ID: <1272067578.9664.40.camel@keith-laptop> (raw)
At long last here is a good data set for filesystem comparison. It is
from 2.6.34-rc3 (unpatched). It compares ext3 ext4 ext4-nobarrier,
btrfs, btrfs-nocow, xfs and jfs on a software raid setup with a decent
spindle count.
http://btrfs.boxacle.net/repository/raid/2010-04-14_2004/2.6.34-rc3/2.6.34-rc3.html
As we know touring barriers off helps a lot with ext4 on this machine.
I think Steve Pratt send some notification to the btrfs folks. Feel free
to point others at this data.
A history from this setup can be found here: (mostly btrfs related
data)
http://btrfs.boxacle.net/repository/raid/history/History.html
I hope to be do these large data set runs once in every major kernel
revision life cycle.
Thanks,
Keith Mannthey
LTC FS-Dev
reply other threads:[~2010-04-24 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1272067578.9664.40.camel@keith-laptop \
--to=kmannth@us.ibm.com \
--cc=linux-ext4@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