From: Glen Holcomb <damnbigman@...>
Date: 2008-07-24T01:36:07+09:00
Subject: Of GUIs threads and scheduling woes

------=_Part_157748_1240356.1216831308370
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I have a small GUI app that I have written the purposes for it's creation
are two-fold and irrelevant.  Here is my problem:

I have two threads aside from the main thread.  One that wakes machines at
scheduled times and another that shuts them down at scheduled times.
Unfortunately Ruby's scheduler seems to care less when a thread actually
wakes up as long as it doesn't wake up early.  Sometimes I have a five
minute (wall time) gap between when the thread should wake and when it
actually does.

The observed behavior seems to be magnified/caused by minimizing the
application.  Does anyone have any suggestions that could lead to a more
responsive app?  5+ minutes late wouldn't matter so much if it didn't cause
the thread to miss an event scheduled a minute or two after the one that was
late.  I suppose I could re-structure my code and may have to.  I was just
hoping that there is a way to get tolerable responsiveness out of a thread.

-Glen

-- 
"Hey brother Christian with your high and mighty errand, Your actions speak
so loud, I can't hear a word you're saying."

-Greg Graffin (Bad Religion)

------=_Part_157748_1240356.1216831308370--