From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
Eduardo Bach <hellbach@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: The performance is not as expected when used several disks on raid0.
Date: Fri, 14 Aug 2015 15:50:26 -0400 [thread overview]
Message-ID: <55CE4682.3080106@gmail.com> (raw)
In-Reply-To: <CAJCQCtTXBYg2zZH3fs3S_kbYHtkvKSjcgoujZrLeTqNW1eRzEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On 2015-08-14 14:31, Chris Murphy wrote:
> On Fri, Aug 14, 2015 at 9:16 AM, Eduardo Bach <hellbach@gmail.com> wrote:
>
>> With btrfs the result approaches 3.5GB/s. When using mdadm+xfs the
>> result reaches 6gb/s, which is the expected value when compared with
>> parallel dd made on discs.
>
> mdadm with what chunk (strip) size? The default for mdadm is 512KiB.
> On Btrfs it's fixed at 64KiB. While testing with 64KiB chunk with XFS
> on md RAID might improve its performance relative to Btrfs, at least
> it's a more apples to apples comparison.
>
I have a feeling that XFS will still win this. It is one of the slower
filesystems for Linux, but it still beats BTRFS senseless when it comes
to performance as of right now.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-08-14 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 15:16 The performance is not as expected when used several disks on raid0 Eduardo Bach
2015-08-14 16:30 ` Calvin Walton
2015-08-14 16:35 ` Calvin Walton
2015-08-17 19:44 ` Eduardo Bach
2015-08-17 20:36 ` Calvin Walton
2015-08-14 18:31 ` Chris Murphy
2015-08-14 19:50 ` Austin S Hemmelgarn [this message]
2015-08-14 19:54 ` Chris Murphy
2015-08-14 19:58 ` Austin S Hemmelgarn
2015-08-15 6:30 ` Duncan
2015-08-17 11:38 ` Austin S Hemmelgarn
2015-08-17 23:06 ` Duncan
2015-08-18 11:34 ` Austin S Hemmelgarn
2015-08-18 14:59 ` Duncan
2015-08-17 19:57 ` Eduardo Bach
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=55CE4682.3080106@gmail.com \
--to=ahferroin7@gmail.com \
--cc=hellbach@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.