Path: utzoo!attcan!uunet!lll-winken!ncis.tis.llnl.gov!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: DEC3100-Xlib performance
Message-ID: <2675@helios.ee.lbl.gov>
Date: 18 May 89 16:14:23 GMT
References: <8905181301.AA00183@expire.lcs.mit.edu> <1201@ttds.UUCP>
Sender: usenet@helios.ee.lbl.gov
Lines: 24

In article <8905181301.AA00183@expire.lcs.mit.edu>, rws@EXPO.LCS.MIT.EDU writes:
> Path: > 
>     When I tried to break this test with ^C's I found out that the system no
>     longer responded, indicating that the X-server had some abnormal priority.
> 
> It probably doesn't have that much to do with priority, although it's possible.
> Your keystrokes have to go through the server to get to the application.  The
> server is busy drawing a bunch of arcs, and isn't paying much attention to your
> input.  This is a matter of scheduling in the server, more than priority.  It
> is possible that your server is running at higher priority than your shell, in
> which case even if the server dispatches the keystrokes they might not get
> processed, since the server will go back to drawing those arcs.

Or possibly ALL of the arc requests have already reached the server and it is
just faithfully carrying out its orders.  
When I start up xfig, if I stop it with a STOP signaljust a few seconds after 
starting it up, the shell says it is stopped, but 10 or 15 seconds later, most
of its windows (widgets) appear on the screen.  All (or most) of the information
has been sent by the client to the server, but the server is still processing it.

_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
We don't need no signatures!