From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
zlang@redhat.com, fstests@vger.kernel.org,
linux-xfs@vger.kernel.org, guan@eryu.me
Subject: Re: [PATCHSET 3/3] xfsprogs: scale shards on ssds
Date: Thu, 6 Jun 2024 22:06:42 -0700 [thread overview]
Message-ID: <ZmKVYsgIkh-h5PG5@infradead.org> (raw)
In-Reply-To: <20240605005636.GI52987@frogsfrogsfrogs>
On Tue, Jun 04, 2024 at 05:56:36PM -0700, Darrick J. Wong wrote:
> Not much other than the AG[IF] and log grant heads becoming less hot.
> That pushes the bottlenecks to the storage device, which indeed is about
> 8 per device. More if you can raid0 them.
>
> *Fortunately* for metadata workloads the logging code is decent about
> deduplicating repeated updates, so unless you're doing something truly
> nasty like synchronous direct writes to a directory tree with parent
> pointers that is being modified heavily, it takes some effort to
> overload the ssd.
>
> (Or a crappy ssd, I guess. Maybe I'll pull out the 860 QVO and see how
> it does.)
Ok. I'm also a little worried about creating lots of AGs for tiny
file systems. Then again I've not actually been able to find the code
yet which I should probably look at first.
next prev parent reply other threads:[~2024-06-07 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 20:12 [PATCHSET 3/3] xfsprogs: scale shards on ssds Darrick J. Wong
2024-06-03 20:13 ` [PATCH 1/1] xfs: test scaling of the mkfs concurrency options Darrick J. Wong
2024-06-04 5:09 ` [PATCHSET 3/3] xfsprogs: scale shards on ssds Christoph Hellwig
2024-06-05 0:56 ` Darrick J. Wong
2024-06-07 5:06 ` Christoph Hellwig [this message]
2024-06-07 18:16 ` Darrick J. Wong
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=ZmKVYsgIkh-h5PG5@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox