Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!super!mjt
From: mjt@super.ORG (Michael J. Tighe)
Newsgroups: comp.unix.wizards
Subject: Re: Cray I/O (was: Re: What kinds of things)
Message-ID: <9853@super.ORG>
Date: 4 Jun 89 14:56:14 GMT
References: <106326@sun.Eng.Sun.COM> <422@ladcgw.ladc.bull.com> <13688@ncoast.ORG> <4609@alvin.mcnc.org> <424@ladcgw.ladc.bull.com> <4616@alvin.mcnc.org> <16618@rpp386.Dallas.TX.US> <873@mtxinu.UUCP> <9989@nuchat.UUCP>
Sender: news@super.ORG
Reply-To: mjt@super.UUCP (Michael J. Tighe)
Distribution: na
Organization: Supercomputing Research Center, Lanham, Md.
Lines: 18

In article <9989@nuchat.UUCP> steve@nuchat.UUCP (Steve Nuchia) writes:
> But mounting an NFS partition from the cray and firing up a
> conventional  editor on the file will result in its contents being
> copied across the wire in both directions, which we were trying to
> avoid.
 
But the "work" is being done by the IOP's and that is what they are
there for. The Cray CPU's are not doing the work, which is what you
want. However, if you use an editor on the Cray, the CPU's are doing
the work. I guess the problem (for you) is one of trading CPU
performance vs network performance. I think if you look at the cost of
your CPU's vs the cost of your network, you will see that you should
be saving your CPU's...
-- 
-------------
Michael Tighe
internet: mjt@super.org
   uunet: ...!uunet!super!mjt