Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!usc!cs.utexas.edu!sun-barr!newstop!sun!sally!plocher
From: plocher@sally.Sun.COM (John Plocher)
Newsgroups: comp.unix.i386
Subject: Re: Tuning Streams
Message-ID: <133063@sun.Eng.Sun.COM>
Date: 19 Mar 90 00:31:21 GMT
References: <4Y62V32xds13@ficc.uu.net> <70400003@m.cs.uiuc.edu>
Sender: news@sun.Eng.Sun.COM
Reply-To: plocher@sun.UUCP (John Plocher)
Organization: Sun Microsystems, Mountain View
Lines: 26

+--
| >> We're experiencing some problems with a network implementation on an intel
| >> 320 running System V/386. The performance is dog slow,  [ ... ]
| Additionally, the problem often manifests itself under NFS, when trying to read
| files. If the file is longer than a certain (small, roughly a few K), nothing
| will be read, while small files will be read just fine. I will get a
+--

Aha!

It sounds like you need to set rsize=1024,wsize=1024 in your /etc/fstab file
for all your NFS devices...

Most/(all?) 386 TCP/IP implementations on ethernet have a max packet size
of 1K, and most other NFS systems assume 8K.  Files under 1K work OK, but
big files fail...

example (this is actually only ONE line in /etc/fstab!):

	sun:/usr/spool/news /usr/spool/news nfs
	    ro,soft,bg,intr,timeo=70,wsize=1024,rsize=1024,retrans=5 0 0

This *is* mentioned in Wollongong's 386 TCP/IP & NFS manuals, I don't know
about LAI,ISC, Everex, or Intel...

   -John Plocher