From: Steven Pratt <slpratt@austin.ibm.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS Performance page
Date: Wed, 22 Oct 2008 08:53:54 -0500 [thread overview]
Message-ID: <48FF3072.7050404@austin.ibm.com> (raw)
In-Reply-To: <20081022001437.GA23949@think.oraclecorp.com>
Chris Mason wrote:
> On Tue, Oct 21, 2008 at 05:20:03PM -0500, Steven Pratt wrote:
>
>> 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.
>>
>
> Very interesting data, thank you for posting this. The first comment
> I'll make is that -o nodatacow requires -o nodatasum. The sums aren't
> valid without the cow.
>
Thought that might be the case. Ok, we will drop this variation.
> The FFSB mail server workload, does it do fsync writes?
>
No, but we have the ability to add that if we choose.
> For the sequential read workload, I'm guessing (hoping) the files are
> created in parallel?
>
Sorry, setup is still single threaded.
Steve
> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-10-22 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 22:20 BTRFS Performance page Steven Pratt
2008-10-22 0:14 ` Chris Mason
2008-10-22 13:53 ` Steven Pratt [this message]
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=48FF3072.7050404@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=chris.mason@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox