From owner-freebsd-current  Wed Jul 19 07:12:55 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id HAA25120
          for current-outgoing; Wed, 19 Jul 1995 07:12:55 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id HAA25112
          ; Wed, 19 Jul 1995 07:12:37 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA23267; Thu, 20 Jul 1995 00:08:07 +1000
Date: Thu, 20 Jul 1995 00:08:07 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199507191408.AAA23267@godzilla.zeta.org.au>
To: bde@zeta.org.au, phk@freefall.cdrom.com
Subject: Re: slow nfsv3 writes
Cc: current@freebsd.org, dfr@render.com, esser@ZPR.Uni-Koeln.DE
Sender: current-owner@freebsd.org
Precedence: bulk

>> 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.

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.

Bruce