Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!uwm.edu!psuvax1!news
From: melling@cs.psu.edu (Michael D Mellinger)
Newsgroups: comp.sys.next
Subject: Re: memory usage (was: (Ne)X(T) Terminals---a hot product idea?
Message-ID: <7e1G6bu.1@cs.psu.edu>
Date: 28 Apr 91 10:41:54 GMT
References: <1991Apr25.084827.1475@math.ucla.edu> <SCOTT.91Apr27094820@texnext.gac.edu>
Sender: news@cs.psu.edu (Usenet)
Distribution: na
Organization: Penn State Computer Science
Lines: 49
In-Reply-To: scott@texnext.gac.edu's message of 27 Apr 91 15:48:20 GMT
Nntp-Posting-Host: sunws8.sys.cs.psu.edu


In article <SCOTT.91Apr27094820@texnext.gac.edu> scott@texnext.gac.edu (Scott Hess) writes:

   I'd still want a disk drive.  Makes it much easier to do software
   updates - remember that NextStep1.0 couldn't do -NXHost to a
   2.0 system, so those would be needed even in the windowserver.
   8MB RAM is still going to be a plus.  The main reason people
   should have 16M on a NeXT is because DPS takes up alot of RAM!
   Right now, I've not got much running on my NextStation (Stuart,
   Edit, Background, IconBounce), so there shouldn't be too
   many windows, right?  The RSIZE of windowserver from ps aux
   reports 2.74M, the VSIZE 20.0M.  So more RAM would be a plus.
   Besides, RAM is getting cheaper as we speak . . .

The output of ps has to be wrong.  Look at the values for csh on the
NeXT.

USER       PID  %CPU %MEM VSIZE RSIZE TT STAT  TIME COMMAND
melling   3204   0.3  2.3 1.34M  384K p8 S     0:01 -csh (csh)

-rwxr-xr-x  1 root     wheel     106496 Oct 22  1990 /bin/csh*


Now compare this with tcsh a SPARC station running Sun OS 4.1.

USER       PID %CPU %MEM   SZ  RSS TT STAT START  TIME COMMAND
melling   1840  0.0  2.4  128  264 p1 S    06:27   0:01 -tcsh (tcsh5.18)

-rwxrwxr-x  1 flee     staff      212992 Jul 17  1990 tcsh5.18*


sunws8<!>% size tcsh5.18
text    data    bss     dec     hex
188416  24576   17008   230000  38270

sunws8<!>% file tcsh5.18
tcsh5.18:       sparc demand paged dynamically linked executable

Now tcsh contains a lot more features than NeXT's version of csh(CMU
shell), and it doesn't take up nearly as much memory on the Sun.
Notice that it is also using shared libaries.

So what gives?

Eric Scott told me that using /usr/etc/vmmprint would give me the
answer, but I haven't really looked at it yet(I noticed that there
isn't a man page for it).

-Mike