From: Josh Triplett <josh@joshtriplett.org>
To: Andreas Dilger <adilger@dilger.ca>
Cc: David Howells <dhowells@redhat.com>,
Theodore Ts'o <tytso@mit.edu>,
"Darrick J. Wong" <djwong@kernel.org>, Chris Mason <clm@fb.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-cachefs@redhat.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
NeilBrown <neilb@suse.com>
Subject: Re: How capacious and well-indexed are ext4, xfs and btrfs directories?
Date: Mon, 21 Jun 2021 17:50:07 -0700 [thread overview]
Message-ID: <YNEzvwgqo6pQ50Pq@localhost> (raw)
In-Reply-To: <B70B57ED-6F11-45CC-B99F-86BBDE36ACA4@dilger.ca>
On Tue, May 25, 2021 at 03:13:52PM -0600, Andreas Dilger wrote:
> There was a patch pushed recently that targets "-o discard" performance:
> https://patchwork.ozlabs.org/project/linux-ext4/list/?series=244091
> that needs a bit more work, but may be worthwhile to test if it improves
> your workload, and help put some weight behind landing it?
I just got a chance to test that patch (using the same storage stack,
with ext4 atop dm-crypt on the same SSD). That patch series makes a
*massive* difference; with that patch series (rebased atop latest
5.13.0-rc7) and the test case from my previous mail, `rm -r testdir`
takes the same amount of time (~17s) whether I have discard enabled or
disabled, and doesn't disrupt the rest of the system. Without the
patch, that same removal took many minutes, and stalled out the rest of
the system.
Thanks for the reference; I'll follow up to the thread for that patch
with the same information.
- Josh Triplett
next prev parent reply other threads:[~2021-06-22 0:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:06 How capacious and well-indexed are ext4, xfs and btrfs directories? David Howells
2021-05-17 23:22 ` Dave Chinner
2021-05-17 23:40 ` Chris Mason
2021-05-19 8:00 ` Avi Kivity
2021-05-19 12:57 ` Dave Chinner
2021-05-19 14:13 ` Avi Kivity
2021-05-18 7:24 ` David Howells
2021-05-21 5:13 ` Andreas Dilger
2021-05-23 5:51 ` Josh Triplett
2021-05-25 4:21 ` Darrick J. Wong
2021-05-25 5:00 ` Christoph Hellwig
2021-05-25 21:13 ` Andreas Dilger
2021-05-25 21:26 ` Matthew Wilcox
2021-05-25 22:13 ` Darrick J. Wong
2021-05-25 22:48 ` Andreas Dilger
2021-05-26 0:24 ` Chris Mason
2021-06-22 0:50 ` Josh Triplett [this message]
2021-05-25 22:31 ` David Howells
2021-05-25 22:58 ` Andreas Dilger
2021-05-26 0:00 ` David Howells
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=YNEzvwgqo6pQ50Pq@localhost \
--to=josh@joshtriplett.org \
--cc=adilger@dilger.ca \
--cc=clm@fb.com \
--cc=dhowells@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=tytso@mit.edu \
/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).