This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author darrenr
Recipients amaury.forgeotdarc, darrenr, wplappert
Date 2008-12-17.22:20:32
SpamBayes Score 0.00168265
Marked as misclassified No
Message-id <1229552434.21.0.237258123286.issue4273@psf.upfronthosting.co.za>
In-reply-to
Content
I think we still need to prevent collectable cycles in our Python code.
Here's the situation:

We've got a process that creates many Python objects, and it needs to be
responsive, it's not good for it to block on one operation for more than
100-200 ms. The automatic garbage collection is currently taking on the
order of 2 seconds for this process.

If we can guarantee that no collectable or non-collectable cycles are
being created, we can gradually increase the collection threshold, or
turn off the garbage collector entirely, reducing or eliminating the
blocking overhead of garbage collection.
History
Date User Action Args
2008-12-17 22:20:34darrenrsetrecipients: + darrenr, amaury.forgeotdarc, wplappert
2008-12-17 22:20:34darrenrsetmessageid: <1229552434.21.0.237258123286.issue4273@psf.upfronthosting.co.za>
2008-12-17 22:20:33darrenrlinkissue4273 messages
2008-12-17 22:20:32darrenrcreate