Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ginosko!gem.mps.ohio-state.edu!apple!agate!shelby!decwrl!gilroy.pa.dec.com!klee
From: klee@gilroy.pa.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: X performance drop
Keywords: plock
Message-ID: <1905@bacchus.dec.com>
Date: 6 Oct 89 18:03:27 GMT
References: <1904@bacchus.dec.com> <1184@krafla.rhi.hi.is>
Sender: news@decwrl.dec.com
Reply-To: klee@decwrl.dec.com
Organization: DEC Western Software Laboratory
Lines: 11

Paul's suggestions are valid, and happen with many X applications.
Another is getting paged out (as opposed to getting a lower priority)
by the OS.  Inactive clients will get paged out, so must be read off
disk before they can respond to user input.  Conversely, active clients
tend to take over physical memory (as inactive clients get page out)
and get considerably faster after a few minutes.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@decwrl.dec.com
uucp: uunet!decwrl!klee