From: Dave Hansen <dave@sr71.net>
To: linux-btrfs@vger.kernel.org, Qu Wenruo <quwenruo@cn.fujitsu.com>,
Chris Mason <clm@fb.com>
Subject: qgroup code slowing down rebalance
Date: Wed, 16 Mar 2016 13:53:15 -0700 [thread overview]
Message-ID: <56E9C7BB.7060509@sr71.net> (raw)
I have a medium-sized multi-device btrfs filesystem (4 disks, 16TB
total) running under 4.5.0-rc5. I recently added a disk and needed to
rebalance. I started a rebalance operation three days ago. It was on
the order of 20% done after those three days. :)
During this rebalance, the disks were pretty lightly used. I would see
a small burst of tens of MB/s, then it would go back to no activity for
a few minutes, small burst, no activity, etc... During the quiet times
(for the disk) one processor would be pegged inside the kernel and would
have virtually no I/O wait time. Also during this time, the filesystem
was pretty unbearably slow. An ls of a small directory would hang for
minutes.
A perf profile shows 92% of the cpu time is being spend in
btrfs_find_all_roots(), called under this call path:
btrfs_commit_transaction
-> btrfs_qgroup_prepare_account_extents
-> btrfs_find_all_roots
So I tried disabling quotas by doing:
btrfs quota disable /mnt/foo
which took a few minutes to complete, but once it did, the disks went
back up to doing ~200MB/s, the kernel time went down to ~20%, and the
system now has lots of I/O wait time. It looks to be behaving nicely.
Is this expected? From my perspective, it makes quotas pretty much
unusable at least during a rebalance. I have a full 'perf record'
profile with call graphs if it would be helpful.
next reply other threads:[~2016-03-16 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:53 Dave Hansen [this message]
2016-03-17 1:36 ` qgroup code slowing down rebalance Qu Wenruo
2016-03-17 16:36 ` Dave Hansen
2016-03-18 1:02 ` Qu Wenruo
2016-03-18 16:33 ` Dave Hansen
2016-03-21 1:44 ` Qu Wenruo
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=56E9C7BB.7060509@sr71.net \
--to=dave@sr71.net \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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.