Date: Wed, 1 Sep 2010 11:46:30 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Hannes Hauswedell <h2+freebsd@fsfe.org> Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? Message-ID: <2070918035.372723.1283355990476.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <201009011339.15898.h2%2Bfreebsd@fsfe.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi everyone, >=20 > I am experiencing similar issues with newnfs: >=20 > 1) I have two clients that each get around 0.5MiB/s to 2.6MiB/s > reading > from the NFS4-share on Gbit-Lan >=20 > 2) Mounting with -t newnfs -o nfsv3 results in no performance gain > whatsoever. >=20 > 3) Mounting with -t nfs results in 58MiB/s ! (Netcat has similar > performance) =E2=86=92 not a hardware/driver issue from my pov >=20 The experimental client does reads in larger MAXBSIZE chunks, which did cause a similar problem in Mac OS X until rsize=3D32768,wsize=3D32768 was specified. Rick already tried that, but you might want to try it for your case. > Is there anything I can do to help fix this? >=20 Ok, so it does sound like an issue in the experimental client and not NFSv4. For the most part, the read code is the same as the regular client, but it hasn't been brought up-to-date with recent changes. One thing you could try is building a kernel without SMP enabled and see if that helps? (I only have single core hardware, so I won't see any SMP races.) If that helps, I can compare the regular vs experimental client for smp locking in the read stuff. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2070918035.372723.1283355990476.JavaMail.root>