[Baypiggies] Web Crawler/Backend Engineer - San Francisco, CA

[Tung Wai Yip]

Sorry Crshonda. I don't mean to hijack your job ads :) As you can see this  
mailing list is very nerdy.

Yes, the issue is about utilizing multicore CPU for computation intensive  
task.

But it is also about writing clever one line remark to make fun of job ads  
;-)

Wai Yip


> On Tue, Feb 02, 2010, Asher Langton wrote:
>> On Feb 2, 2010, at 2:14 PM, Aahz wrote:
>>> On Tue, Feb 02, 2010, Tung Wai Yip wrote:
>>>>
>>>> I think my experience tells me don't build multi-threaded
>>>> applications in Python ;-)
>>>
>>> Why?  I've had about equal trouble with multi-processing and
>>> multi-threading.
>>
>> In short: multi-threading is really bad in Python 2.x when the threads
>> are CPU-bound.
>
> Absolutely.  Well, almost -- it's still really good for creating a
> responsive GUI application.  See my Fibonacci example in my threads
> tutorial.
>
> Nevertheless, that's completely different from "don't use threads".
>
> PS: you can remove the "2.x" from your comment; even if the Unladen
> Swallow people improve GIL handling, it's almost certain that CPU-bound
> threads will still be subpar.