Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!chalmers.se!appli!niklas
From: niklas@appli.se (Niklas Hallqvist)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS performance
Keywords: Interactive comments and vs. Novell
Message-ID: <1388@appli.se>
Date: 2 Jun 91 00:19:17 GMT
References: <427@fjcp60.GOV> <1991May28.151439.3167@Firewall.Nielsen.Com>
Organization: Applitron Datasystem AB, GOTHENBURG, SWEDEN
Lines: 32

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.  The
>problem appears to be in either the Streams modules or the TCP and NFS code
>itself.

>ISC's NFS is also an older revision, and doesn't support root-remapping on a
>mount-point basis.

>Blech.

These figures chocked me and I didn't believe it first, so I had to check them.
Truely enough, I got only 25k/sec on transfer from a SCO Unix to an ISC 2.0.2.
The other way around it was 200k/sec, that's an order of magnitude involved here!
What startles me is that I think Lachman has written the NFS implementation for
both SCO and ISC, but that might be wrong.  But if it is not, I think ISC should
get in touch with Lachman and talk about an upgrade of ISC's NFS.  If that will
not happen, our company seriously has to reconsider the choice of ISC over SCO,
as I'm sure others will too, now that this fact has come to the net's attention.
This problem would've caused me lots of performance problems very soon, if I
had not seen this message, thanks Karl.  Yeah, I know I should've done some
benchmarking before deciding OS on our short-to-be backup-server, but lazyness
is one of my great virtues (at least Larry Wall thinks that's a virtue...).

						Niklas

-- 
Niklas Hallqvist	Phone: +46-(0)31-40 75 00
Applitron Datasystem	Fax:   +46-(0)31-83 39 50
Molndalsvagen 95	Email: niklas@appli.se
S-412 63  GOTEBORG, Sweden     mcsun!sunic!chalmers!appli!niklas