Text editors under UNICOS?

[Keith Bierman - SPD Languages Marketing -- MTS]

In article <27289 at ames.arc.nasa.gov> lamaster at ames.arc.nasa.gov (Hugh LaMaster) writes:
>
>1) It is more cost effective to edit on another system, counting the cost
>of moving the file over to be edited via the network, etc.  Don't forget
>the cost of reading the entire file from disk on the Cray,
>writing it over the network, reading it back, and writing it to disk, not
>to mention the CPU and memory utilization by the network layer in the kernel,
>etc.  Then, add the incremental cost of providing computing 
>resources on your editing machine.
>
>2) The cost *savings* (if any) are in any way significant, as a percentage of
>dollars and/or CPU utilization on the system, on the system in question,
>looking at the amount of editing that people are actually doing.
>

It will all depend on how your network is configured, how large your
files are and how much editing we are talking about. 

If the files start out on a front end (say a sun4/390 :>) with NFS and
all that, editing locally may be quite cheap. And if you are doing
massive edits over several hours, you may not care about "start up
time"

If the files are huge, the edits are minor and the communication costs
are high (say the files live directly on the Cray) clearly running
emacs (vi, asoft's tpu or whatever) on the Cray is a win.

I used to copy files over a 1200 baud line from a VAX down to a Mac
... if I was going to work on a file for any length of time ...
because that made my lifer easier. When I only wanted to tweak a line
or two, I used SOS ... the point should be how to maximize work
accomplished/satisfaction with the environment.

cheers
Keith H. Bierman      |*My thoughts are my own. Only my work belongs to Sun*
It's Not My Fault     |	Marketing Technical Specialist    ! kbierman at sun.com
I Voted for Bill &    |   Languages and Performance Tools. 
Opus  (* strange as it may seem, I do more engineering now     *)