[BangPypers] Ideas for Python concurrency...

Santosh Rajan santrajan at gmail.com
Tue Feb 8 09:49:34 CET 2011


Have you considered using queue's with multiprocessing?

On Tue, Feb 8, 2011 at 2:15 PM, Vishal <vsapre80 at gmail.com> wrote:
> On Tue, Feb 8, 2011 at 2:10 PM, Baishampayan Ghose <b.ghose at gmail.com>wrote:
>
>> > Mutliprocessing means, data copying, talking to each other through PIPES,
>> > also it has its issues with running on Windows (all function calls should
>> be
>> > pickelable)
>> >
>> > Threads seems pretty stable on most platforms where Python runs.
>>
>> Threads won't help you much because of the Python GIL.
>>
>> Regards,
>> BG
>>
>> --
>> Baishampayan Ghose
>> b.ghose at gmail.com
>> '
>>
>
> The GIL is only limited to one interpreter. GIL comes into picture because
> Threads in python create a new interpreter context, so the same interpreter
> switches to new byte codes. The original idea was to create a new
> interpreter for each thread, each one with its own GIL !!!. All within the
> same process.
>
> Vishal
> _______________________________________________
> BangPypers mailing list
> BangPypers at python.org
> http://mail.python.org/mailman/listinfo/bangpypers
>



-- 
http://about.me/santosh.rajan


More information about the BangPypers mailing list