[Baypiggies] Web Crawler/Backend Engineer - San Francisco, CA
alecf at flett.org
Wed Feb 3 04:26:34 CET 2010
Wait, you guys (Aahz too?) have to see the full Dave Beazly talk! He really
knows his stuff, too.
Yes, it's basically single threaded on a single CPU machine... but in the
talk he demonstrates how performance goes down dramatically as you add CPUs
- basically the threads end up spending more time fighting for the GIL than
actually use it, because multiple CPUs actually allow them to fight. On a
single core machine, they play nicely and just take turns.
I'd be really interested in seeing the Aahz's FIbbonaci example on a 8x
machine with 7 threads working on Fibbonaci and one doing the UI :) I
suspect it will actually slow to a crawl.
Even Guido thought the talk was "amazing":
On Tue, Feb 2, 2010 at 4:20 PM, wesley chun <wescpy at gmail.com> wrote:
> >> In short: multi-threading is really bad in Python 2.x when the threads
> are CPU-bound.
> some will even argue it *isn't* multithreading in this degenerative
> case... it's just round-robin.
> -- wesley
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> "Python Web Development with Django", Addison Wesley, (c) 2009
> wesley.j.chun :: wescpy-at-gmail.com
> python training and technical consulting
> cyberweb.consulting : silicon valley, ca
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Baypiggies