RetroSearch Browse

Mon May 17 20:59:16 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-May/100141.html

Antoine Pitrou <solipsis at pitrou.net> wrote:

> On Mon, 17 May 2010 11:15:49 PDT
> Bill Janssen <janssen at parc.com> wrote:
> > 
> > What I did know was that
> > some of our big complicated Python multi-threaded daemons had shown
> > puzzling resource hogging when moved from small Macs to large 8-core
> > machines with hardware RAID and lots of memory.
> 
> Could you give detailed information about this?

Probably not detailed enough.  IP issues.  It's a version of UpLib.

> Since you're talking about a "big complicated Python multi-threaded
> daemon", I presume you can't port it to Python 3 very quickly, but it
> would be nice to know if the problem disappears with 3.2.

Yes, it would.  As soon as I have working 3.x versions of BeautifulSoup,
PIL, ReportLab, JCC, pylucene, pyglet, nltk, email, epydoc, feedparser,
dictclient, docutils, hachoir, mutagen, medusa, python-dateutil, and
vobject, I'll let you know. :-)

> There /has/ been momentum in fixing it. In py3k.

Yes, I specifically meant in the 2.x branch.  I'm guessing I'll have to
stay on 2.x for at least 5 more years, due to the other package
dependencies.

Bill

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-May/100141.html below:

[Python-Dev] Fixing the GIL (with a BFS scheduler)