On Wed, Mar 19, 2008 at 11:25 AM, Stefan Ring <[EMAIL PROTECTED]> wrote: > Adam Olsen <rhamph <at> gmail.com> writes: > > > > So you want responsiveness when idle but throughput when busy? > > Exactly ;) > > > > Are those calculations primarily python code, or does a C library do > > the grunt work? If it's a C library you shouldn't be affected by > > safethread's increased overhead. > > > > It's Python code all the way. Frankly, it's a huge mess, but it would be very > very hard to come up with a scalable solution that would allow to optimize > certain hotspots and redo them in C or C++. There isn't even anything left to > optimize in particular because all those low hanging fruit have already been > taken care of. So it's just ~30kloc Python code over which the total time > spent > is quite uniformly distributed :(.
I see. Well, at this point I think the most you can do is file a bug so the problem doesn't get forgotten. If nothing else, if my safethread stuff goes in it'll very likely include a --with-gil option, so I may put together a FIFO scheduler. -- Adam Olsen, aka Rhamphoryncus _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
