Date: Sat, 4 Sep 2010 12:55:28 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: rick-freebsd2009@kiwi-computer.com Cc: Hannes Hauswedell <h2+freebsd@fsfe.org>, freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? Message-ID: <1144621878.493708.1283619328514.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20100904023550.GB47730@rix.kiwi-computer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- > On Wed, Sep 01, 2010 at 11:46:30AM -0400, Rick Macklem wrote: > > > > > > I am experiencing similar issues with newnfs: > > > > > > 1) I have two clients that each get around 0.5MiB/s to 2.6MiB/s > > > reading > > > from the NFS4-share on Gbit-Lan > > > > > > 2) Mounting with -t newnfs -o nfsv3 results in no performance gain > > > whatsoever. > > > > > > 3) Mounting with -t nfs results in 58MiB/s ! (Netcat has similar > > > performance) ??? not a hardware/driver issue from my pov > > > > 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. > > Do you (or will you soon) have some patches I/we could test? I'm > willing to try anything to avoid mounting ten or so subdirectories in > each of my mount points. > One other thing you could do is run this in a loop while you have a slow read running. The client threads must be blocked somewhere a lot if the read rate is so slow. (Then take a look at "xxx" and please email it to me too.) ps axHl >> xxx sleep 1 rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1144621878.493708.1283619328514.JavaMail.root>