From owner-freebsd-current Wed Jul 19 07:39:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id HAA25807 for current-outgoing; Wed, 19 Jul 1995 07:39:12 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id HAA25792 ; Wed, 19 Jul 1995 07:39:04 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id PAA23535; Wed, 19 Jul 1995 15:23:12 +0100 Date: Wed, 19 Jul 1995 15:23:11 +0100 (BST) From: Doug Rabson To: Bruce Evans cc: bde@zeta.org.au, phk@freefall.cdrom.com, current@freebsd.org, esser@zpr.uni-koeln.de Subject: Re: slow nfsv3 writes In-Reply-To: <199507191408.AAA23267@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@freebsd.org Precedence: bulk On Thu, 20 Jul 1995, Bruce Evans wrote: > >> I was getting 9K/sec for writes before I complained and this change > >> was made :-). > > >How about running a snoop and get some per-packet times ? > > `iozone 1 8192' on a 486DX2/66 over lo0 reports reading at > 1775129 bytes/sec and writing at 111227 bytes/sec. tcpdump reports > about 4ms for reading 8292 bytes and about 70ms for writing 8320 > bytes. > > The problem was that this is actually for nfsv2. For some reason I > thought that nfsv3 would be the default. I think the default should be for mount_nfs to attempt a v3 mount rpc and if that fails, then fall back to v2. > > Under nfsv3, `iozone 4 8192' reports ... oops it hangs on netio and > other processes hang on nfsrcvlk and after a little while other > processes hang on ufslk2 ... This is probably the same problem > that Doug saw. I haven't had a chance to look at this yet. I am in Windows95 mode at the moment :-( -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939