Date: Mon, 21 Oct 2024 19:52:46 +0100 From: void <void@f-m.fm> To: freebsd-fs@freebsd.org Subject: Re: improving nfs client & server performance Message-ID: <Zxai_n-LhohogSEY@int21h> In-Reply-To: <CAM5tNy4scNutJXdOL=UmK_NhObcfbwpnUpL1dFqe3JVeJVWvcQ@mail.gmail.com> References: <ZxZbPmv_11tS5pxZ@int21h> <CAM5tNy4scNutJXdOL=UmK_NhObcfbwpnUpL1dFqe3JVeJVWvcQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Rick, thanks for replying On Mon, Oct 21, 2024 at 09:17:05AM -0700, Rick Macklem wrote: >There are lots of possibilities, but here are a couple to try... >vfs.zfs.dmu_offset_next_sync=0 - this makes SEEK_HOLE/SEEK_DATA >much faster, but less reliable (as in it might miss finding a hole) >vfs.nfsd.cachetcp=0 - this disables the DRC cache for TCP connections >(if this helps, there are settings to try to tune he DRC). >Disabling the DRC for TCP means that there is a >slight chance of corruption, due to duplicate >non-idempotent RPCs being done after a TCP reconnect. Has no >effect on NFSv4.1/4.2 mounts. How can I tell what version NFS mount it has? rpcinfo nfs-server-ip shows versions 4,3,2,1 --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Zxai_n-LhohogSEY>