Xref: utzoo comp.sys.3b1:250 comp.sys.att:11785
Path: utzoo!mnetor!tmsoft!torsqnt!hybrid!scifi!bywater!uunet!zaphod.mps.ohio-state.edu!usc!srhqla!denwa!stb!michael
From: michael@stb.info.com (Michael Gersten)
Newsgroups: comp.sys.3b1,comp.sys.att
Subject: Re: Unix pc sluggishness when switching windows (long)
Message-ID: <1991Feb11.023209.15112@stb.info.com>
Date: 11 Feb 91 02:32:09 GMT
References: <1991Feb5.040416.354@shibaya.lonestar.org> <979@gnosys.svle.ma.us> <1991Feb7.161712.9239@shibaya.lonestar.org> <1991Feb9.011213.8868@blilly.UUCP>
Organization: The Serial Tree BBS, +1 213 397 3137
Lines: 23

In article <1991Feb9.011213.8868@blilly.UUCP> bruce@balilly.UUCP (Bruce Lilly) writes:
>  F S    UID   PID  PPID  C PRI NI ADR SZ:RSZ   WCHAN   STIME  TTY  TIME COMD
<3.5 meg machine, good speed>
>  1 S   root   157     1  3  27 20 220169: 35   54f14  Jan 11   w3 52:11 wmgr
<2 meg machine, slow speed>
>  1 S   root   234     1  7  27 20  a5 60:  0   5af14  Jan 13   w3 16:52 wmgr
<2 meg machine, good speed>
>  1 S   root   234     1  7  27 20  a5 61: 56   5af14  Jan 13   w3 17:06 wmgr

What these have in common is the RESIDENT size of wmgr. The slow speed
on the middle one is because wmgr is completely swapped out on the disk.
So any suspend/resume activity causes it to be swapped in. Both of the
other cases have wmgr resident in memory (or at least enough of it).

A recently restarted wmgr has a smaller working set size needed to switch.
Therefore, it will be faster.

		Michael

-- 
		Michael
michael@stb.info.com denwa!stb!michael anes.ucla.edu!stb!michael 
"Space is an illusion; disk space doubly so"