Multiprocessing, shared memory vs. pickled copies

John Nagle nagle at
Mon Apr 11 09:21:42 CEST 2011

On 4/10/2011 3:29 PM, sturlamolden wrote:
> On 10 apr, 18:27, John Nagle<na... at>  wrote:
>>      Unless you have a performance problem, don't bother with shared
>> memory.
>>      If you have a performance problem, Python is probably the wrong
>> tool for the job anyway.
> Then why does Python have a multiprocessing module?

     Because nobody can fix the Global Interpreter Lock problem in CPython.

     The multiprocessing module is a hack to get around the fact
that Python threads don't run concurrently, and thus, threaded
programs don't effectively use multi-core CPUs.

				John Nagle

More information about the Python-list mailing list