darrenr <python-roun...@dranalli.com> added the comment: 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. _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue4273> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
