From: Chris Mason <chris.mason@fusionio.com>
To: Kaspar Schleiser <kaspar@schleiser.de>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Chris Mason <clmason@fusionio.com>
Subject: Re: experimental raid5/6 code in git
Date: Tue, 12 Feb 2013 10:30:54 -0500 [thread overview]
Message-ID: <20130212153054.GA16687@shiny.masoncoding.com> (raw)
In-Reply-To: <511A5CE1.60309@schleiser.de>
On Tue, Feb 12, 2013 at 08:16:49AM -0700, Kaspar Schleiser wrote:
> Hey Chris,
>
> On 02/02/2013 05:02 PM, Chris Mason wrote:
> > Btrfs -- 604MB/s
> > MD -- 162MB/s
> >
> >
> > MD -- 800MB/s very little system time
> > Btrfs -- 3.8GB/s one CPU mostly pegged
>
> > Btrfs -- 380MB/s seen by fio
> > MD -- 174MB/s seen by fio
>
> > Creating 12 million files on Btrfs raid5 took 226 seconds, vs 485
> > seconds on MD.
>
> Do I read these numbers incorrectly, or does even this first iteration
> of btrfs' raid5/6 code run circles around MD?
Yes and no. Most of the differences were on flash, and really it just
looks like MD needs tuning for IO latency and concurrency. There are
some MD patches for this recently to add more threads for parity
calculations, and these solve some throughput problems.
But one thing that we've proven with btrfs is that helper threads mean
more IO latencies. So the MD code probably needs some short cuts to do
the parity inline as well.
-chris
prev parent reply other threads:[~2013-02-12 15:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 16:02 experimental raid5/6 code in git Chris Mason
2013-02-03 17:33 ` Hendrik Friedel
2013-02-04 21:42 ` H. Peter Anvin
2013-02-05 1:23 ` Chris Mason
2013-02-05 2:26 ` H. Peter Anvin
2013-02-05 2:59 ` Gareth Pye
2013-02-05 5:29 ` Chester
2013-02-05 6:10 ` Gareth Pye
2013-02-05 14:22 ` Tomasz Torcz
2013-02-05 18:32 ` Chris Mason
[not found] ` <CAM_ZMPCAcKtOH4UapR8HbSN6Woi7Lh7mqy+e14TDY+8tM386iQ@mail.gmail.com>
2013-02-11 15:13 ` Chris Mason
2013-02-12 15:16 ` Kaspar Schleiser
2013-02-12 15:30 ` Chris Mason [this message]
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=20130212153054.GA16687@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=kaspar@schleiser.de \
--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.