views:

838

answers:

3

I've got a thread that's polling a piece of hardware.

while not hardware_is_ready():
    pass
process_data_from_hardware()

But there are other threads (and processes!) that might have things to do. If so, I don't want to burn up cpu checking the hardware every other instruction. It's been a while since I've dealt with threading, and when I did it wasn't Python, but I believe most threading libraries have a yield function or something that allows a thread to tell the scheduler "Give the other threads a chance."

while not hardware_is_ready():
    threading.yield()          # This function doesn't exist.
process_data_from_hardware()

But I can't find any reference to something like this in the threading documentation. Python does have a yield statement, but I'm pretty sure that's something else entirely (to do with generators).

What's the correct thing to do here?

+6  A: 

Read up on the Global Interpreter Lock (GIL).

For example: http://jessenoller.com/2009/02/01/python-threads-and-the-global-interpreter-lock/

Also: http://www.pyzine.com/Issue001/Section_Articles/article_ThreadingGlobalInterpreter.html

Do this in your code if you must do Busy Waiting (e.g. polling a device).

time.sleep( 0.0001 )

This will yield to the thread scheduler.

Also, I collected some notes and references in http://homepage.mac.com/s_lott/iblog/architecture/C551260341/E20081031204203/index.html

S.Lott
I'm no expert, but I've read a bit on the GIL. Could you give me a hint what in particular relates to this question?I'll go with `time.sleep(epsilon)` for now, but it's kind of unsatisfying, isn't it? There isn't any particular interval I want to sleep for.
Tom Future
Its the only solution if your hardware cannot send interrupts.
Unknown
A: 

If you're doing this on *nix, you might find the select library useful. Kamaela also has a few components you may find useful, but it may require a bit of a paradigm change.

Jason Baker
+6  A: 

time.sleep(0) is sufficient to yield control -- no need to use a positive epsilon. Indeed, time.sleep(0) MEANS "yield to whatever other thread may be ready".

Alex Martelli
Is this documented somewhere? I thought this might be true -- I've seen it in other languages -- but I couldn't find a mention of it in the Python docs.
Tom Future
for example, http://docs.python.org/library/sched.html "delayfunc will also be called with the argument 0 after each event is run to allow other threads an opportunity to run in multi-threaded applications." (delayfunc is usually time.sleep here). I agree it would be nicer if it was documented more directly in module time;-)
Alex Martelli
Well hidden! Thanks!
Tom Future