From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Martin Raiber <martin@urbackup.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Multiple btrfs-cleaner threads per volume
Date: Thu, 2 Nov 2017 11:07:40 -0400 [thread overview]
Message-ID: <fa6917cf-5251-16bb-48c9-e69163ccf530@gmail.com> (raw)
In-Reply-To: <0102015f7d418aa6-af3c2ae7-27b0-47d0-a4bb-173f55304bb9-000000@eu-west-1.amazonses.com>
On 2017-11-02 11:02, Martin Raiber wrote:
> Hi,
>
> snapshot cleanup is a little slow in my case (50TB volume). Would it
> help to have multiple btrfs-cleaner threads? The block layer underneath
> would have higher throughput with more simultaneous read/write requests.
I think a bigger impact would be proper parallelization of IO requests.
Right now, writes are serialized (they first get sent to one device,
then the next, then the next, until they've been sent to all devices),
and reads aren't inherently load-balanced across devices (ideally, other
things than load, like where the last read came from on a rotational
device, would be factored in, but even just regular load balancing would
be an improvement right now). As a result, multi-device BTRFS volumes
in general don't perform as well as possible, which is then compounded
by other issues (such as snapshot cleanup being somewhat expensive).
next prev parent reply other threads:[~2017-11-02 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 15:02 Multiple btrfs-cleaner threads per volume Martin Raiber
2017-11-02 15:07 ` Austin S. Hemmelgarn [this message]
2017-11-02 15:10 ` Hans van Kranenburg
2017-11-02 15:26 ` Martin Raiber
2017-11-02 16:56 ` Hans van Kranenburg
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=fa6917cf-5251-16bb-48c9-e69163ccf530@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@urbackup.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;
as well as URLs for NNTP newsgroup(s).