[Python-ideas] solving multi-core Python

Sturla Molden sturla.molden at gmail.com
Thu Jun 25 01:47:07 CEST 2015

On 25/06/15 00:56, Eric Snow wrote:

> Why?  Because there are enough caveats and performance downsides (see
> Dave Beazley's PyCon 2015 talk) that most folks stop trying to
> rationalize, throw their hands up, and say "Python concurrency stinks"
> and "you can't *really* do multicore on Python".

Yes, that seems to be the case.

> To change this perception we need to give folks a simpler, performant
> concurrency model that takes advantage of multiple cores.  My proposal
> is all about doing at least *something* that makes Python's multi-core
> story obvious and undeniable.

I think the main issue with subinterpreters and a message-passing model 
is that it will be very difficult to avoid deep copies of Python 
objects. And in that case all we have achieved compared to 
multiprocessing is less scalability.

Also you have not removed the GIL, so the FUD about the dreaded GIL will 
still be around. Clearly introducing multiprocessing in the standard 
library did nothing to reduce this.


More information about the Python-ideas mailing list