On Sat, 2024-01-13 at 01:19 +0100, Dan Shelton wrote: > 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. > I guess your clients are trying to do a long pathwalk in a single COMPOUND? Is this the windows client? At first glance, I don't see any real downside to increasing that value. Maybe we can bump it to 100 or so? What would probably be best is to propose a patch so we can discuss the change formally. Cheers, -- Jeff Layton <jlayton@xxxxxxxxxx>
