Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!crdgw1!uunet!mcsun!ukc!acorn!unipalm!ian
From: ian@unipalm.uucp (Ian Phillipps)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS performance
Keywords: Interactive comments and vs. Novell
Message-ID: <1991May31.172221.5282@unipalm.uucp>
Date: 31 May 91 17:22:21 GMT
References: <1991May28.151439.3167@Firewall.Nielsen.Com> <7678@spdcc.SPDCC.COM> <1991May30.165457.26093@unipalm.uucp> <1991May30.204517.14832@Firewall.Nielsen.Com>
Organization: Unipalm Ltd., Cambridge, England
Lines: 31

kdenning@genesis.Naitc.Com (Karl Denninger) writes:

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

Sorry - not reading carefully enough.

I just tried it - 25k/second, using the NFS server on the ISC.
Not too sure of the block size settings, but it tallies with the performance
given above.

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

We have a very slow Sun...