Xref: utzoo comp.windows.x:36656 comp.sys.att:12299
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!hsdndev!cmcl2!prism.poly.edu!drubin
From: drubin@prism.poly.edu (Dave Rubin)
Newsgroups: comp.windows.x,comp.sys.att
Subject: X Clients eating up CPU
Message-ID: <1991May21.201138.1592@prism.poly.edu>
Date: 21 May 91 20:11:38 GMT
Reply-To: drubin@prism.poly.edu (Dave Rubin)
Organization: Polytechnic University, New York
Lines: 23


We are using AT&T 730X X-Windows terminals running XR4 clients off a
Convex C120.  The AT&T terminals operate in both standard and X-Windows
mode, with a feature to toggle back and forth.

The problem is, when the terminals are left in standard mode, the X-Windows
server is in a stop mode.  Therefore, clients cannot communicate with the
server during this time, causing a large number of messages to be queued.
Clients (such as xclock and xload) eat up a very large amount of CPU time
and memory when trying to communicate with the stopped server.  I suspect
that the clients are constantly trying to send messages to the server,
with no delay between retries.

Is there any way, such as an X Server or toolkit option, to limit the
client's activity when trying to communicate with a dormant server?  Or
is there some way to combat this problem on the 730X?

Any info would be appreciated ... please respond through E-mail.

--
Dave Rubin
Polytechnic University
drubin@prism.poly.edu