Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!Firewall!genesis!kdenning
From: kdenning@genesis.Naitc.Com (Karl Denninger)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS performance
Summary: Note the direction here
Keywords: Interactive comments and vs. Novell
Message-ID: <1991May30.204517.14832@Firewall.Nielsen.Com>
Date: 30 May 91 20:45:17 GMT
References: <1991May28.151439.3167@Firewall.Nielsen.Com> <7678@spdcc.SPDCC.COM> <1991May30.165457.26093@unipalm.uucp>
Sender: news@Firewall.Nielsen.Com (Usenet News)
Organization: AC Nielsen Co., Bannockburn IL
Lines: 32
Nntp-Posting-Host: genesis.naitc.com

In article <1991May30.165457.26093@unipalm.uucp> ian@unipalm.uucp (Ian Phillipps) writes:
>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?
>
>No: I just copied /unix from an ISC 386 to a Sun 3/50 (yeah!) in 6 seconds
>elapsed; thats approx 120k/second.

Note the direction here.

You were READING from the ISC machine.

Now try to copy it the other direction.  You'll either (1) hang TCP/IP,
if you have the default buffer size, or (2) get horrible throughput if
you're using the 1k block size.

The Sun will swamp the ISC machine's protocol stack, and blow it sky high
with 8k (actually, anything more than 1k) block size.

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