*BSD News Article 3805


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!metro!news
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: X386 far too busy?
Message-ID: <1992Aug18.083413.12774@ucc.su.OZ.AU>
Sender: news@ucc.su.OZ.AU
Nntp-Posting-Host: physics.su.oz.au
Organization: School of Physics, University of Sydney, Australia
References: <1992Aug17.211128.7958@novatel.cuc.ab.ca>
Date: Tue, 18 Aug 1992 08:34:13 GMT
Lines: 30

In article <1992Aug17.211128.7958@novatel.cuc.ab.ca> hpeyerl@novatel.cuc.ab.ca (Herb Peyerl) writes:
>Hi...
>
>I started the server about 18 hours ago and left it with only 
>two xterm's, an icon box, and an xclock running... There was
>basically no activity all night.  This morning I did a "ps -agx"
>and noticed that X386 had racked up 1145:23.29 CPU (minutes?)... 
>That's sort of horrendous isn't it?  I'm presently typing on an
>Apollo DN3500 running an X11R4 server... The node's been up since
>July 16th and is the node I work on all day long every day and it's
>only racked up 465 CPU minutes...
>
>I'm wondering if there's something brutal going on in the X386 server...
>I mean, I realize that an ET3000 is not your typically fast card
>but XTerm's are REALLY grim... Maybe I'm just used to this Apollo
>(which, on it's own is not overly impressive compared to say an 
>HP720...)
>
>I dunno... Just wondering if anyone else has noticed this?

Try applying the com.c patch posted a little while back.  The problem
is that select() keeps telling the server you've moved the mouse even
when you haven't.

David
--
------------------------------------------------------------------------------
 David Dawes (dawes@physics.su.oz.au)    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------