Newsgroups: comp.protocols.nfs
Path: utzoo!utgpu!watserv1!watmath!att!linac!Firewall!genesis!kdenning
From: kdenning@genesis.Naitc.Com (Karl Denninger)
Subject: Re: NFS performance
Message-ID: <1991May30.045522.6246@Firewall.Nielsen.Com>
Summary: It can be, and it is
Keywords: Interactive comments and vs. Novell
Sender: news@Firewall.Nielsen.Com (Usenet News)
Nntp-Posting-Host: genesis.naitc.com
Organization: AC Nielsen Co., Bannockburn IL
References: <427@fjcp60.GOV> <1991May28.151439.3167@Firewall.Nielsen.Com> <7678@spdcc.SPDCC.COM>
Date: Thu, 30 May 91 04:55:22 GMT

In article <7678@spdcc.SPDCC.COM> rbraun@spdcc.COM (Rich Braun) writes:
>kdenning@genesis.Naitc.Com (Karl Denninger) writes:
>>ISC's NFS is horrid.  The best I've seen on writes is about 30k/sec on a
>>fast '386 machine.  The CPU is not saturated, nor is the Ethernet card.
>
>SOSS is almost that fast, running on an 8-bit card with a 20-MHz 386
>and talking to a Novell server through a second network hop, using 1K
>RPC writes.  ISC can't be *that* bad, can it?

It will also hang the TCP stack entirely if you mount a ISC disk from a Sun
(or other real workstation) with 8k read/write block sizes and blast a few
hundred K of data back and forth.

If you run 1k blocks, it works.  VERY slowly.

PCs can't load it heavily enough to crash it, but they run real slow.

Yes, ISC's NFS is really that bad (This is 2.2 with or without their
"update" installed).

I'd love a REAL NFS implementation on top of a Real Unix for the 386.  It
doesn't exist to the best of my knowledge.

--
Karl Denninger - AC Nielsen, Bannockburn IL (708) 317-3285
kdenning@nis.naitc.com

"The most dangerous command on any computer is the carriage return."
Disclaimer:  The opinions here are solely mine and may or may not reflect
  	     those of the company.