Date: Wed, 14 Oct 1998 11:52:14 -0400 (EDT) From: Brian Feldman <green@zone.syracuse.NET> To: Mike Smith <mike@smith.net.au> Cc: "Alex G. Bulushev" <bag@sinbin.demos.su>, Daniel Rock <rock@cs.uni-sb.de>, current@FreeBSD.ORG Subject: Re: -current NFS problem Message-ID: <Pine.BSF.4.05.9810141151120.14822-100000@zone.syracuse.NET> In-Reply-To: <199810141530.IAA00811@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Perhaps this could be the problem with NFS "hanging" certain people all the time? (not the pine thing) The system spending way too much time inside the kernel transmitting NFS packets.... Brian Feldman On Wed, 14 Oct 1998, Mike Smith wrote: > > another known problem exist for nfsv3 > > > > we use www server working over nfs with about 1500000 hits/day > > it work fine with nfsv2 (load 0.1 - 0.8), but with nfsv3 > > we see load > 130 and server replay is very slow ... > > i think this is a bug in fbsd nfsv3 realization, the > > same scheme with solaris/sparc nfsv3 client/server work > > without this problems ... > > The problem here is almost certainly that we don't cache the results of > ACCESS RPC calls. There's an outstanding request from NetApp for us to > address this; their testing indicates that 80% or more of NFS traffic > generated by FreeBSD systems consists of ACCESS RPC calls. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9810141151120.14822-100000>