Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!well!rchrd
From: rchrd@well.UUCP (Richard Friedman)
Newsgroups: comp.unix.cray
Subject: Re: Text editors under UNICOS?
Message-ID: <12295@well.UUCP>
Date: 21 Jun 89 17:23:16 GMT
References: <571@orange19.qtp.ufl.edu> <BOB.89Jun15171538@tinman.cis.ohio-state.edu> <4713@alvin.mcnc.org> <27289@ames.arc.nasa.gov>
Reply-To: rchrd@well.UUCP (Richard Friedman)
Organization: Pacific-Sierra Research (Berkeley)
Lines: 26

In article <27289@ames.arc.nasa.gov> lamaster@ames.arc.nasa.gov (Hugh LaMaster) writes:
>What is lacking is hard evidence that "editing" is a problem in the first
>place.  But, just speculating, my experience is that the most precious
>resource on Crayxyz's is not interrupts or CPU, but memory, so I guess that if
>you were looking for a problem you might try to demonstrate that editing
>is hurting your memory utilization and causing a significant increase in
>swapping.
>
Hugh: MY experience is that editing directly on the CRAY is
VERY frustrating  (UNICOS).  I have to log in via phonelines
or networks and the delays both with UNICOS swapping and network
make working with VI (say) almost impossible.  Having to wait
a few seconds for responses leads to real confusion.  And
editing mistakes.  For small editing situations (changing a few
syntax errors for example) its alright.  But any extensive
restructuring of a program I'd rather edit it on my workstation
and use KERMIT to upload to the Cray.  The problem is trying to
do critical work (like editing) in a timesharing environment.
What I have done is build a small testbed in my Apollo so I 
can develop codes locally and only later bring them to the
Cray.  But then again, my Cray isn't in the next room.
(Its 3Kmiles away).
-- 
 ...Richard Friedman           rchrd@well.uucp                      
    (Pacific-Sierra Research/Berkeley, CA.)
     also: {lll-crg,pacbell,hplabs}!well!rchrd