I'm looking for a little bit of clarification. NFSD_SERVERS, per the man page controls:
"the maximum number of concurrent NFS requests that the server can handle." Is a request represented by a unique TCP connection (assuming in this case NFSv3 via TCP) or does it represent a single comand (GETATTR, SETATTR, etc) on an existing session? I have a somewhat busy NFS server handling approximately 2200 or so read/write reqeusts per second (per nfsstat -v 3 1). There are only about 30 open NFS TCP sessions however (per netstat -n | grep 2049). I'm wondering if I should bump my NFSD_SERVERS from 1024 to something higher to improve performance? Is there a way (via dtrace or other) to determine how many of NFSD_SERVERS are in use? I'm also not completely clear whether or not NFSD_LISTEN_BACKLOG has to do with new TCP sessions established or as a queue for individual NFS requests commands. Thanks, Ray _______________________________________________ nfs-discuss mailing list [email protected]
