From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: 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: Mon, 3 Jun 2024 22:09:10 -0700 [thread overview]
Message-ID: <Zl6hdo1ZXQwg2aM0@infradead.org> (raw)
In-Reply-To: <171744525781.1532193.10780995744079593607.stgit@frogsfrogsfrogs>
On Mon, Jun 03, 2024 at 01:12:05PM -0700, Darrick J. Wong wrote:
> This patchset adds a different computation for AG count and log size
> that is based entirely on a desired level of concurrency. If we detect
> storage that is non-rotational (or the sysadmin provides a CLI option),
> then we will try to match the AG count to the CPU count to minimize AGF
> contention and make the log large enough to minimize grant head
> contention.
Do you have any performance numbers for this?
Because SSDs still have a limited number of write streams, and doing
more parallel writes just increases the work that the 'blender' has
to do for them. Typical number of internal write streams for not
crazy expensive SSDs would be at most 8.
next prev parent reply other threads:[~2024-06-04 5:09 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 ` Christoph Hellwig [this message]
2024-06-05 0:56 ` [PATCHSET 3/3] xfsprogs: scale shards on ssds Darrick J. Wong
2024-06-07 5:06 ` Christoph Hellwig
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=Zl6hdo1ZXQwg2aM0@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