From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
Nazar Mokrynskyi <nazar@mokrynskyi.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Major HDD performance degradation on btrfs receive
Date: Wed, 16 Mar 2016 07:53:24 -0400 [thread overview]
Message-ID: <56E94934.4030306@gmail.com> (raw)
In-Reply-To: <CAJCQCtRuLPBH5ELvVS5aP+gww5ZXrWN-inj_dgV4se+Jr4NJCg@mail.gmail.com>
On 2016-03-16 02:51, Chris Murphy wrote:
> On Tue, Mar 15, 2016 at 10:23 PM, Nazar Mokrynskyi <nazar@mokrynskyi.com> wrote:
>> Sounds like a really good idea!
>>
>> I'll try to implement in in my backup tool, but it might take some time to
>> see real benefit from it (or no benefit:)).
>
> There is a catch. I'm not sure how much testing deleting 100
> subvolumes at once gets. It should work. I haven't looked in xfstests
> to see how much of this is being tested. So it's possible you're
> testing it. So be ready.
I've actually tested bulk removal of large numbers of snapshots multiple
times before (it's actually one of the things that isn't in xfstests
that I check when testing patches, I usually test power of two groups
from 16 up to 256 at a time). It works, but it may tie up most of the
disk bandwidth for a while depending on what type of storage you're using.
next prev parent reply other threads:[~2016-03-16 11:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 19:58 Major HDD performance degradation on btrfs receive Nazar Mokrynskyi
2016-02-22 23:30 ` Duncan
2016-02-23 17:26 ` Marc MERLIN
2016-02-23 17:34 ` Marc MERLIN
2016-02-23 18:01 ` Lionel Bouton
2016-02-23 18:30 ` Marc MERLIN
2016-02-23 20:35 ` Lionel Bouton
2016-02-24 10:01 ` Patrik Lundquist
2016-02-23 16:55 ` Nazar Mokrynskyi
2016-02-23 17:05 ` Alexander Fougner
2016-02-23 17:18 ` Nazar Mokrynskyi
2016-02-23 17:29 ` Alexander Fougner
2016-02-23 17:34 ` Nazar Mokrynskyi
2016-02-23 18:09 ` Austin S. Hemmelgarn
2016-02-23 17:44 ` Nazar Mokrynskyi
2016-02-24 22:32 ` Henk Slager
2016-02-24 22:46 ` Nazar Mokrynskyi
[not found] ` <ce805cd7-422c-ab6a-fbf8-18a304aa640d@mokrynskyi.com>
2016-02-25 1:04 ` Henk Slager
2016-03-15 0:47 ` Nazar Mokrynskyi
2016-03-15 23:11 ` Henk Slager
2016-03-16 3:37 ` Nazar Mokrynskyi
2016-03-16 4:18 ` Chris Murphy
2016-03-16 4:23 ` Nazar Mokrynskyi
2016-03-16 6:51 ` Chris Murphy
2016-03-16 11:53 ` Austin S. Hemmelgarn [this message]
2016-03-16 20:58 ` Chris Murphy
2016-03-16 4:22 ` Chris Murphy
2016-03-17 7:00 ` Duncan
2016-03-18 14:22 ` Nazar Mokrynskyi
2016-05-27 1:57 ` Nazar Mokrynskyi
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 19:39 Nazar Mokrynskyi
2016-02-16 4:44 Nazar Mokrynskyi
2016-02-16 9:10 ` Duncan
2016-02-18 18:19 ` Henk Slager
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=56E94934.4030306@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=nazar@mokrynskyi.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.