Path: utzoo!utgpu!watserv1!watmath!att!rutgers!apple!agate!ucbvax!brl.mil!mike
From: mike@brl.mil (Mike Muuss)
Newsgroups: comp.unix.cray
Subject: Re:  "vi" & Supercomputer Performance
Message-ID: <9010180045.aa04646@WOLF.BRL.MIL>
Date: 18 Oct 90 04:45:51 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 19

Dan -

The problem with using NFS is that, in the scenario under discussion,
the Cray would be required to NFS transfer the *entire* file to the
editor running on the workstation, and then receive the *entire* file
back to the Cray again using NFS.

For changing a few lines in a medium-sized source file, this is STILL
more expensive of Cray time than running the editor locally on the Cray.

For highly modularized source code, where the source files are only
a few dozen Kbytes, using NFS in this way is certainly a performance "win".
But running a GREP through your sources via NFS is likely to be a big
loose.

Face it, folks:  using the Cray interactively in the edit-compile-test
cycle is a good, efficient use of time.  Both Cray time and user time.
	Best,
	 -Mike