From: jeffm@suse.com
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: check improve 'checking extents' scalability
Date: Thu, 23 Jun 2016 15:26:03 -0400 [thread overview]
Message-ID: <1466709966-31506-1-git-send-email-jeffm@suse.com> (raw)
From: Jeff Mahoney <jeffm@suse.com>
While running xfstests generic/291, which creates a single file populated
with reflinks to the same extent, I found that fsck had been running for
hours. perf top lead me to find_data_backref as the culprit, and a litte
more digging made it clear: For every extent record we add, we iterate
the entire list first. My test case had ~2M records. That math doesn't
go well.
This patchset converts the extent_backref list to an rbtree. The test
that used to run for more than 8 hours without completing now takes
less than 20 seconds.
-Jeff
---
Jeff Mahoney (3):
btrfs-progs: check: add helpers for converting between structures
btrfs-progs: check: supplement extent backref list with rbtree
btrfs-progs: check: switch to iterating over the backref_tree
cmds-check.c | 355 +++++++++++++++++++++++++++++++++++++++--------------------
1 file changed, 237 insertions(+), 118 deletions(-)
--
2.7.1
next reply other threads:[~2016-06-23 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 19:26 jeffm [this message]
2016-06-23 19:26 ` [PATCH 1/3] btrfs-progs: check: add helpers for converting between structures jeffm
2016-06-23 19:26 ` [PATCH 2/3] btrfs-progs: check: supplement extent backref list with rbtree jeffm
2016-06-23 19:26 ` [PATCH 3/3] btrfs-progs: check: switch to iterating over the backref_tree jeffm
2016-06-23 21:24 ` [PATCH 0/3] btrfs-progs: check improve 'checking extents' scalability Holger Hoffstätte
2016-06-23 21:38 ` Jeff Mahoney
2016-07-04 12:20 ` David Sterba
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=1466709966-31506-1-git-send-email-jeffm@suse.com \
--to=jeffm@suse.com \
--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).