Brett Cannon wrote:
> On 9/17/06, *Nick Coghlan* <[EMAIL PROTECTED]
> - use threads to perform blocking I/O in parallel
> - use multiple interpreters to perform Python execution in parallel
>
>
> Possibly, but as it stands now interpreters just execute in their own
> Python thread, so there is no real performance boost. Without the GIL
> shifting over to per interpreter instead of per process there is going
> to be the same performance problems as with Python threads. And
> changing that would be hard since objects can be shared between
> multiple interpreters.
I was thinking it would be easier to split out the Global Interpreter Lock and
a per-interpreter Local Interpreter Lock, rather than trying to go to a full
free-threading model. Anyone sharing other objects between interpreters would
still need their own synchronisation mechanism, but something like
threading.Queue should suffice for that.
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
_______________________________________________
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
