[Xastir-dev] Xastir a CPU pig again?

[Curt Mills, WE7U]

On Thu, 25 Dec 2003, Tom Russo wrote:

> I just finished a quick study in reducing the 100ms delay down to 10ms
> and then 1ms.  No CPU bogging here.  Drop it down one more decade to 100us 
> and kaboom.

That's what I was waiting for.

Looking at the comments in that routine (which I probably wrote), it
doesn't matter all that much what the delay is as long as it doesn't
cause problems by being too small.  If it were a one second delay or
a ten second delay, we'd still catch downed sockets.

Looks like I was getting a bit too aggressive at trying to remove
dumb delays, and didn't slow down to read the comments in that
particular section while I was doing it.  Kind'a tells you how much
I hate blind delays I suppose...

I'll bump it back up.  Way up.  The delay is just there to jump out
of the thread if the socket goes down.  Other than that, we should be
waiting in the select(), taking no CPU to speak of, while we're
waiting for some data to come in on the socket.

-- 
Curt, WE7U.				archer at eskimo.com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"