Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!sdd.hp.com!news.cs.indiana.edu!maytag!mks.com!alex
From: alex@mks.com (Alex White)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS performance
Keywords: Interactive comments and vs. Novell
Message-ID: <1991May30.021412.22925@mks.com>
Date: 30 May 91 02:14:12 GMT
References: <427@fjcp60.GOV> <1991May28.151439.3167@Firewall.Nielsen.Com> <7678@spdcc.SPDCC.COM>
Organization: Mortice Kern Systems, Waterloo, Ontario, CANADA
Lines: 25

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?
>
>-rich


Can't be *that* bad?  Sure can!
However, I've found that the CPU is indeed saturated.
Thats on a 33Mhz 386 with a 16bit ethernet card.
Mind you, I was also trying to figure out why backing up over
the network (rsh ISCmachine 'find | cpio' >/dev/rmt0) and after
breaking it all down, found even the find by itself with no network
traffic used a good healthy hunk of the cpu.  Personally, I think ISC
just has a horridly slow nami().

Does anybody know if any of the fancy dandy ethernet cards with tcp/ip
on them have any kind of driver that would work?  And would they end up
faster?  [If the problem is in streams or something, maybe; but if its
in nami() not a hope!]