From: Dan Shelton <dan.f.shelton@gmail.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Increasing NFSD_MAX_OPS_PER_COMPOUND to 96
Date: Sat, 13 Jan 2024 01:19:45 +0100 [thread overview]
Message-ID: <CAAvCNcDtTNDRvUVjUy4BE7eBCgmkb6hfkq3P0jaGDC=OXg0=6g@mail.gmail.com> (raw)
Hello!
We've been experiencing significant nfsd performance problems with a
customer who has a deeply nested filesystem hierarchy, lots of
subdirs, some of them 60-80 dirs deep (!!), which leads to an
exponentially slowdown with nfsd accesses.
Some of the issues have been addressed by implementing a better
directory walker via multiple dir fds and openat() (instead of just
cwd+open()), but the nfsd side still was a pretty dramatic issue,
until we bumped #define NFSD_MAX_OPS_PER_COMPOUND in
linux-6.7/fs/nfsd/nfsd.h from 50 to 96. After that the nfsd side
behaved MUCH more performant.
Dan
--
Dan Shelton - Cluster Specialist Win/Lin/Bsd
next reply other threads:[~2024-01-13 0:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 0:19 Dan Shelton [this message]
2024-01-13 1:32 ` Increasing NFSD_MAX_OPS_PER_COMPOUND to 96 Jeff Layton
2024-01-13 1:47 ` Dan Shelton
2024-01-13 1:53 ` Chuck Lever III
2024-01-13 2:40 ` Rick Macklem
2024-01-13 7:20 ` Roland Mainz
[not found] ` <CAKAoaQmmEv+HRjmBMrSMGZn9RQr8C=2W4yeX4vNnohXFJPCV5A@mail.gmail.com>
[not found] ` <65a29ca8.6b0a0220.ad415.d6d8.GMR@mx.google.com>
[not found] ` <CAKAoaQkZ+b7NfrVi=gu1vCJBvv10=k85bG_kZV9G3jE45OOquw@mail.gmail.com>
2024-01-13 15:09 ` kernel.org list issues... / was: Fwd: Turn NFSD_MAX_* into tuneables ? / was: " Jeff Layton
2024-01-13 16:10 ` Chuck Lever III
2024-01-13 21:14 ` Jeff Layton
2024-01-13 23:09 ` Chuck Lever III
2024-01-14 17:50 ` Cedric Blancher
2024-01-14 20:22 ` Chuck Lever III
2024-01-18 1:56 ` RFE: Linux nfsd's |ca_maxoperations| should be at *least* |64| ... / was: " Roland Mainz
2024-01-18 9:44 ` Martin Wege
2024-01-18 14:52 ` Chuck Lever III
2024-03-16 11:55 ` |ca_maxoperations| - tuneable ? / was: " Roland Mainz
2024-03-16 13:16 ` Roland Mainz
2024-03-16 16:35 ` Chuck Lever III
2024-03-19 6:25 ` Cedric Blancher
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='CAAvCNcDtTNDRvUVjUy4BE7eBCgmkb6hfkq3P0jaGDC=OXg0=6g@mail.gmail.com' \
--to=dan.f.shelton@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).