From: Steven Pratt <slpratt@austin.ibm.com>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS Performance page
Date: Tue, 21 Oct 2008 17:20:03 -0500 [thread overview]
Message-ID: <48FE5593.2080209@austin.ibm.com> (raw)
As discussed on the BTRFS conference call, myself and Kevin Corry have
set up some test machines for the purpose of doing performance testing
on BTRFS. The intent is to have a semi permanent setup that we can use
to test new features and code drops in BTRFS as well as to do
comparisons to other file systems. The systems are pretty much fully
automated for execution, so we should be able to crank out large numbers
of different benchmarks as well as keep up with GIT changes.
The data is hosted at http://btrfs.boxacle.net/. So far we have the data
for the single disk tests uploaded. We should be able to upload results
from the larger RAID config tomorrow.
Initial tests were done with the FFSB benchmark and we picked 5 common
workloads; create, random and sequential read, random write, and a mail
server emulation. We plan to expand this based on feedback to include
more FFSB tests and/or other workloads.
All runs have complete analysis data with them (iostat, mpstat,
oprofile, sar), as well as the FFSB profiles that can be used to
recreate any test we ran. We also have collected blktrace data but not
uploaded due to size.
Please follow the results link on the bottom of the main page to get to
the current results. Let me know what you like or don't like. I will
post again when we get the RAID data uploaded.
Steve
next reply other threads:[~2008-10-21 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 22:20 Steven Pratt [this message]
2008-10-22 0:14 ` BTRFS Performance page Chris Mason
2008-10-22 13:53 ` Steven Pratt
2008-10-22 14:05 ` Chris Mason
2008-10-22 15:00 ` Steven Pratt
2008-10-22 15:19 ` Chris Mason
2008-10-22 15:45 ` Steven Pratt
2008-10-22 15:55 ` Chris Mason
2008-10-22 19:25 ` Paul P Komkoff Jr
2008-10-22 19:46 ` Steven Pratt
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=48FE5593.2080209@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=linux-btrfs@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 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.