[concurrency] Inside the Python GIL
jeremy.mcmillan at gmail.com
Fri Jun 12 21:45:43 CEST 2009
Proof is in the pudding. If you can cook up a load test, under what
conditions can you soak up all of your CPU's cycles?
On Jun 12, 2009, at 12:39 PM, skip at pobox.com wrote:
> Jeremy> I'm not sure I understand how to distinguish between I/
> O bound
> Jeremy> threads and CPU bound threads.
> I don't know that we can (people writing bits of Python which
> operate on
> threads). I suspect a useful distinction though is that an I/O
> bound thread
> mostly gives up the CPU to wait on an I/O device, while a CPU bound
> is mostly "evicted" from the CPU by the OS scheduler. (Though I
> sort of
> suspect you already understand this textbook definition.) Is that
> you're referring to by "not sure I understand"?
> concurrency-sig mailing list
> concurrency-sig at python.org
More information about the concurrency-sig