Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!bu.edu!bu-cs!buengc!bph
From: bph@buengc.BU.EDU (Blair P. Houghton)
Newsgroups: comp.unix.ultrix
Subject: Re: Managing a network of UNIX workstations
Message-ID: <5295@buengc.BU.EDU>
Date: 15 Jan 90 21:36:32 GMT
References: <3949@jhunix.HCF.JHU.EDU> <9338@cbmvax.commodore.com> <12938@watcgl.waterloo.edu> <4624@helios.ee.lbl.gov> <12943@watcgl.waterloo.edu>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.unix.ultrix
Organization: Boston Univ. Col. of Eng.
Lines: 18

In article <12943@watcgl.waterloo.edu> idallen@watcgl.waterloo.edu (Ian! D. Allen [CGL]) writes:
>In article <4624@helios.ee.lbl.gov> envbvs@epb2.lbl.gov (Brian V. Smith) writes:
>>Both the source and object files are stored on the remote NFS server and
>>there never seems to be too much of a network load because of this.
>
>We don't have a problem with network load either.  The compiles and such
>just take twice as long over NFS as doing them right on the local disk.

But that was the original complainant's point; that he was in a
software development environment, where you might want to do
fifty fix-and-compile iterations each day, and having to wait
twice as long would, of course, halve your productivity.

				--Blair
				  "Or worse, if you have a
				   habit of going into the
				   Usenet window while cc
				   is running..."