From: Christian Rohmann <crohmann@netcologne.de>
To: Chris Murphy <lists@colorremedies.com>,
"Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core?
Date: Mon, 1 Feb 2016 15:10:51 +0100 [thread overview]
Message-ID: <56AF676B.2070902@netcologne.de> (raw)
In-Reply-To: <CAJCQCtT9NZdaJ8MKHQw-1ARi7PkLeq_p9dtdZaPYdLt8EpTcbA@mail.gmail.com>
Hey Chris,
sorry for the late reply.
On 01/27/2016 10:53 PM, Chris Murphy wrote:
> I can't exactly reproduce this. I'm using +C qcow2 on Btrfs on one SSD
> to back the drives in the VM.
>
> 2x btrfs raid1 with files totalling 5G consistently takes ~1 minute
> [1] to balance (no filters)
>
> 4x btrfs raid6 with the same files *inconsistently* takes ~1m15s [2]
> to balance (no filters)
> iotop is all over the place, from 21MB/s writes to 527MB/s
To be honest, 5G is not really 21T spread across 12 spindles with LOTS
of data on them. On another box with 8x4TB spinning rust it's also very
slow.
> Do both of you get something like this:
> [root@f23m ~]# dmesg | grep -i raid
> [ 1.518682] raid6: sse2x1 gen() 4531 MB/s
> [ 1.535663] raid6: sse2x1 xor() 3783 MB/s
> [ 1.552683] raid6: sse2x2 gen() 10140 MB/s
> [ 1.569658] raid6: sse2x2 xor() 7306 MB/s
> [ 1.586673] raid6: sse2x4 gen() 11261 MB/s
> [ 1.603683] raid6: sse2x4 xor() 7009 MB/s
> [ 1.603685] raid6: using algorithm sse2x4 gen() 11261 MB/s
> [ 1.603686] raid6: .... xor() 7009 MB/s, rmw enabled
> [ 1.603687] raid6: using ssse3x2 recovery algorithm
Yes:
--- cut ---
[ 4.704396] raid6: sse2x1 gen() 4288 MB/s
[ 4.772401] raid6: sse2x1 xor() 4036 MB/s
[ 4.840403] raid6: sse2x2 gen() 7629 MB/s
[ 4.908405] raid6: sse2x2 xor() 6247 MB/s
[ 4.976404] raid6: sse2x4 gen() 10221 MB/s
[ 5.044397] raid6: sse2x4 xor() 7620 MB/s
[ 5.044525] raid6: using algorithm sse2x4 gen() 10221 MB/s
[ 5.044641] raid6: .... xor() 7620 MB/s, rmw enabled
[ 5.044767] raid6: using ssse3x2 recovery algorithm
--- cut ---
Would some sort of stracing or profiling of the process help to narrow
down where the time is currently spent and why the balancing is only
running single-threaded?
Regards
Christian
next prev parent reply other threads:[~2016-02-01 14:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 13:38 btrfs-progs 4.4 re-balance of RAID6 is very slow / limited to one cpu core? Christian Rohmann
2016-01-22 14:51 ` Duncan
2016-01-24 2:30 ` Henk Slager
2016-01-25 11:34 ` Christian Rohmann
2016-01-25 22:13 ` Chris Murphy
[not found] ` <CAKZK7uxdX9UBPOKButtPjqBOdVUfHdRTimP+W34fkz1h9P+wHg@mail.gmail.com>
2016-01-26 0:44 ` Fwd: " Justin Brown
2016-01-26 5:17 ` Chris Murphy
2016-01-26 6:14 ` Chris Murphy
2016-01-26 8:54 ` Christian Rohmann
2016-01-26 19:26 ` Chris Murphy
2016-01-26 19:27 ` Chris Murphy
2016-01-26 19:57 ` Austin S. Hemmelgarn
2016-01-26 20:20 ` Chris Murphy
2016-01-27 8:48 ` Christian Rohmann
2016-01-27 16:34 ` Austin S. Hemmelgarn
2016-01-27 20:58 ` bbrendon
2016-01-27 21:53 ` Chris Murphy
2016-01-28 12:27 ` Austin S. Hemmelgarn
2016-02-01 14:10 ` Christian Rohmann [this message]
2016-02-01 20:52 ` Chris Murphy
2016-02-09 13:48 ` Christian Rohmann
2016-02-09 16:46 ` Marc MERLIN
2016-02-09 21:46 ` Chris Murphy
2016-02-10 2:23 ` Chris Murphy
2016-02-10 2:36 ` Chris Murphy
2016-02-10 13:19 ` Christian Rohmann
2016-02-10 19:16 ` Chris Murphy
2016-02-10 19:38 ` Chris Murphy
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=56AF676B.2070902@netcologne.de \
--to=crohmann@netcologne.de \
--cc=ahferroin7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).