From: David Howells <dhowells@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
"Darrick J. Wong" <djwong@kernel.org>, Chris Mason <clm@fb.com>
Cc: dhowells@redhat.com, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org
Subject: How capacious and well-indexed are ext4, xfs and btrfs directories?
Date: Mon, 17 May 2021 16:06:58 +0100 [thread overview]
Message-ID: <206078.1621264018@warthog.procyon.org.uk> (raw)
Hi,
With filesystems like ext4, xfs and btrfs, what are the limits on directory
capacity, and how well are they indexed?
The reason I ask is that inside of cachefiles, I insert fanout directories
inside index directories to divide up the space for ext2 to cope with the
limits on directory sizes and that it did linear searches (IIRC).
For some applications, I need to be able to cache over 1M entries (render
farm) and even a kernel tree has over 100k.
What I'd like to do is remove the fanout directories, so that for each logical
"volume"[*] I have a single directory with all the files in it. But that
means sticking massive amounts of entries into a single directory and hoping
it (a) isn't too slow and (b) doesn't hit the capacity limit.
David
[*] What that means is netfs-dependent. For AFS it would be a single volume
within a cell; for NFS, it would be a particular FSID on a server, for
example. Kind of corresponds to a thing that gets its own superblock on the
client.
next reply other threads:[~2021-05-17 15:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:06 David Howells [this message]
2021-05-17 23:22 ` How capacious and well-indexed are ext4, xfs and btrfs directories? Dave Chinner
2021-05-17 23:40 ` Chris Mason
2021-05-18 7:24 ` David Howells
2021-05-19 8:00 ` Avi Kivity
2021-05-19 12:57 ` Dave Chinner
2021-05-19 14:13 ` Avi Kivity
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
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=206078.1621264018@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=clm@fb.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=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