From: Trond Myklebust <trondmy@hammerspace.com>
To: "chuck.lever@oracle.com" <chuck.lever@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"neilb@suse.com" <neilb@suse.com>
Subject: Re: knfsd performance
Date: Tue, 18 Jun 2024 19:29:55 +0000 [thread overview]
Message-ID: <754f3e0f6f962cbd46b2b22e87d9de9f8b285ab4.camel@hammerspace.com> (raw)
In-Reply-To: <58A84B36-C121-46F8-ABCB-BE4F212E9C81@oracle.com>
On Tue, 2024-06-18 at 18:40 +0000, Chuck Lever III wrote:
>
>
> > On Jun 18, 2024, at 2:32 PM, Trond Myklebust
> > <trondmy@hammerspace.com> wrote:
> >
> > I recently back ported Neil's lwq code and sunrpc server changes to
> > our
> > 5.15.130 based kernel in the hope of improving the performance for
> > our
> > data servers.
> >
> > Our performance team recently ran a fio workload on a client that
> > was
> > doing 100% NFSv3 reads in O_DIRECT mode over an RDMA connection
> > (infiniband) against that resulting server. I've attached the
> > resulting
> > flame graph from a perf profile run on the server side.
> >
> > Is anyone else seeing this massive contention for the spin lock in
> > __lwq_dequeue? As you can see, it appears to be dwarfing all the
> > other
> > nfsd activity on the system in question here, being responsible for
> > 45%
> > of all the perf hits.
>
> I haven't seen that, but I've been working on other issues.
>
> What's the nfsd thread count on your test server? Have you
> seen a similar impact on 6.10 kernels ?
>
640 knfsd threads. The machine was a supermicro 2029BT-HNR with 2xIntel
6150, 384GB of memory and 6xWDC SN840.
Unfortunately, the machine was a loaner, so cannot compare to 6.10.
That's why I was asking if anyone has seen anything similar.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2024-06-18 19:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 18:32 knfsd performance Trond Myklebust
2024-06-18 18:40 ` Chuck Lever III
2024-06-18 19:29 ` Trond Myklebust [this message]
2024-06-18 19:39 ` Chuck Lever III
2024-06-18 19:50 ` Trond Myklebust
2024-06-18 19:54 ` Chuck Lever III
2024-06-18 20:16 ` Jeff Layton
2024-06-18 23:17 ` NeilBrown
2024-06-18 23:26 ` Chuck Lever III
2024-06-18 23:33 ` Jeff Layton
2024-06-18 23:51 ` Chuck Lever III
2024-06-19 2:56 ` Dave Chinner
2024-06-19 5:47 ` Christoph Hellwig
2024-06-19 13:44 ` Chuck Lever III
2024-06-19 21:16 ` NeilBrown
2024-06-19 0:42 ` Dave Chinner
2024-06-19 1:01 ` NeilBrown
2024-06-19 21:25 ` NeilBrown
2024-06-20 2:29 ` Dave Chinner
2024-06-20 10:18 ` Jeff Layton
2024-06-20 21:39 ` NeilBrown
2024-06-20 18:33 ` Chuck Lever III
2024-06-20 22:04 ` NeilBrown
2024-06-20 23:57 ` Trond Myklebust
2024-06-18 19:38 ` Jeff Layton
2024-06-18 23:12 ` NeilBrown
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=754f3e0f6f962cbd46b2b22e87d9de9f8b285ab4.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.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