Date: Mon, 21 Oct 2024 14:46:38 +0100 From: void <void@f-m.fm> To: freebsd-fs@freebsd.org Subject: improving nfs client & server performance Message-ID: <ZxZbPmv_11tS5pxZ@int21h>
next in thread | raw e-mail | index | archive | help
I'm looking to try to improve nfs client & server performance. The problem I'm seeing is that when clients access the server, if more than one does it at once, the access speed is very 'spiky' and in /var/log/messages on the client, it has things like Oct 20 07:21:55 kernel: nfs server 192.168.1.10:/zroot/share: not responding Oct 20 07:21:55 kernel: nfs server 192.168.1.10:/zroot/share: is alive again Oct 20 07:42:05 kernel: nfs server 192.168.1.10:/zroot/share: not responding Oct 20 07:42:05 kernel: nfs server 192.168.1.10:/zroot/share: is alive again Oct 20 08:29:54 kernel: nfs server 192.168.1.10:/zroot/share: not responding If one client is accessing one file at once, the transfer is very fast. But syncing like rsync or webdav is very problematic and takes much longer than it should. The server is recent 14-stable and exports nfs via the zfs sharenfs property. The clients are a mix of freebsd and linux (debian) I note on the server there's lots of vfs.nfsd sysctl tunables but I'm not sure if thay are relevant in a zfs sharenfs context. There's even more vfs.zfs but nothing pertaining directly to nfs. On a freebsd client, it has these in rc.conf # nfs client stuff nfs_client_enable="YES" Maybe it needs local locks (-L) unsure how to pass flags to the client started in this way. How would I know if local locks were needed? I note in defaults/rc.conf there is nfs_bufpackets="" # bufspace (in packets) for client but I'm not sure what the effects would be. I've so far set 'zfs set sync=disabled' for the particular vdev and 'sysctl vfs.nfsd.maxthreads=256' on the server, about to test this. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZxZbPmv_11tS5pxZ>