From: James Courtier-Dutton <james.dutton@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs balance problems
Date: Sat, 6 Jan 2018 18:09:58 +0000 [thread overview]
Message-ID: <CAAMvbhFUAQ7M2CET5gdmgGsF-FLZMYviSQusdB8s1ObdXZwzDg@mail.gmail.com> (raw)
In-Reply-To: <pan$ef2b8$3487070c$fddf5d1f$59a5a7a2@cox.net>
On 28 December 2017 at 00:39, Duncan <1i5t5.duncan@cox.net> wrote:
>
> AFAIK, ionice only works for some IO schedulers, not all. It does work
> with the default CFQ scheduler, but I don't /believe/ it works with
> deadline, certainly not with noop, and I'd /guess/ it doesn't work with
> block-multiqueue (and thus not with bfq or kyber) at all, tho it's
> possible it does in the latest kernels, since multi-queue is targeted to
> eventually replace, at least as default, the older single-queue options.
>
> So which scheduler are you using and are you on multi-queue or not?
>
Thank you. The install had defaulted to deadline.
I have now switched it to CFQ, and the system is much more
responsive/interactive now during a btrfs balance.
I will test it when I next get a chance, to see if that has helped me.
After reading about it:
deadline: more likely to complete long sequential reads/writes and
not switch tasks.Thus reducing the amount of seeking but impacting
concurrent tasks.
cfq: more likely to break up long sequential reads/writes to permit
other tasks to do some work. Thus increasing the amount of seeking but
helping concurrent tasks.
This would explain why "cfq" is best for me.
I have not yet looked at "multi-queue".
next prev parent reply other threads:[~2018-01-06 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 11:19 btrfs balance problems James Courtier-Dutton
2017-12-23 11:56 ` Alberto Bursi
[not found] ` <CAAMvbhHV=BvRLv14U0JRrYmhiXeREOTNiVLPkuq=MO6dH4jDiQ@mail.gmail.com>
2017-12-27 21:39 ` James Courtier-Dutton
2017-12-27 21:54 ` waxhead
2017-12-28 0:39 ` Duncan
2017-12-30 0:34 ` Kai Krakow
2018-01-06 18:09 ` James Courtier-Dutton [this message]
2017-12-28 11:15 ` Nikolay Borisov
2017-12-30 0:43 ` 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=CAAMvbhFUAQ7M2CET5gdmgGsF-FLZMYviSQusdB8s1ObdXZwzDg@mail.gmail.com \
--to=james.dutton@gmail.com \
--cc=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).