Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Calvin Walton <calvin.walton@kepstin.ca>
To: Eduardo Bach <hellbach@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: The performance is not as expected when used several disks on raid0.
Date: Mon, 17 Aug 2015 16:36:41 -0400	[thread overview]
Message-ID: <1439843801.24704.11.camel@kepstin.ca> (raw)
In-Reply-To: <CANCCtjk2+DevkJqZB2opVpx9EWRWSM7R1nTigs0z=3jWbH-VMg@mail.gmail.com>

On Mon, 2015-08-17 at 16:44 -0300, Eduardo Bach wrote:
> Based on previous testing with a smaller number of disk I'm
> suspecting
> that the 32 disks are not all being used. With 12 discs I got more
> speed with btrfs thanmdadm+xfs. With, btrfs, 12 disks and large files
> we got the entire theoretical speed, 12 x 200MB/s per disk. My hope
> was to get some light from you guys to debug the problem so the btrfs
> use the 32 discs (assuming this is the problem). Perhaps the debug
> this problem may be of interest to devs?

>From the sounds of this, you must be hitting some bottleneck in the
btrfs code. One thing I'm actually curious about: How is the CPU usage
during these tests?

Btrfs can more work on the CPU than mdadm+xfs - in particular, data che
cksums are enabled by default. If you have compression enabled, that
would obviously be a major hit as well. Make sure you don't have
compression enabled (it's off by default, or you can use the mount
option "compress=no"). You could try with the "nodatasum" option to see
if checksums make a difference.

It could be possible that you're saturating the CPU, and that's why
you're not seeing any additional gains over 3.5GB/s. Taking a look at
top output while the test is running might be informative.

On the other hand, if the CPU isn't saturated and the disk io isn't
saturated, then it's probably a scaling issue in btrfs, possibly
something like lock contention.

-- 
Calvin Walton <calvin.walton@kepstin.ca>


  reply	other threads:[~2015-08-17 20:36 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 [this message]
2015-08-14 18:31 ` Chris Murphy
2015-08-14 19:50   ` Austin S Hemmelgarn
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=1439843801.24704.11.camel@kepstin.ca \
    --to=calvin.walton@kepstin.ca \
    --cc=hellbach@gmail.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