Date: Mon, 21 Oct 2024 15:52:12 -0700 From: Rick Macklem <rick.macklem@gmail.com> To: freebsd-fs@freebsd.org Subject: Re: improving nfs client & server performance Message-ID: <CAM5tNy5j6RknwbvcXjCDs02r1JEO4_De3mY8JHrxYNb0nKhNrw@mail.gmail.com> In-Reply-To: <Zxai_n-LhohogSEY@int21h> References: <ZxZbPmv_11tS5pxZ@int21h> <CAM5tNy4scNutJXdOL=UmK_NhObcfbwpnUpL1dFqe3JVeJVWvcQ@mail.gmail.com> <Zxai_n-LhohogSEY@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 21, 2024 at 11:53=E2=80=AFAM void <void@f-m.fm> wrote: > > 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=3D0 - this makes SEEK_HOLE/SEEK_DATA > >much faster, but less reliable (as in it might miss finding a hole) > > >vfs.nfsd.cachetcp=3D0 - 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 On the clients type: # nfsstat -m rick > -- >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM5tNy5j6RknwbvcXjCDs02r1JEO4_De3mY8JHrxYNb0nKhNrw>