[Python-Dev] C API for gc.enable() and gc.disable() (original) (raw)

Kevin Jacobs jacobs@bioinformed.com bioinformed at gmail.com
Sat Jun 21 17:33:14 CEST 2008

On Sat, Jun 21, 2008 at 11:20 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:

In general, any solution of the "do GC less often" needs to deal with cases where lots of garbage gets produced in a short amount of time (e.g. in a tight loop), and which run out of memory when GC is done less often.

Idea 1: Allow GC to run automatically no more often than n CPU seconds, n being perhaps 5 or 10. Idea 2: Allow GC to run no more often than f(n) CPU seconds, where n is the time taken by the last GC round.

These limits could be reset or scaled by the GC collecting more than n% of the generation 0 objects or maybe the number of PyMalloc arenas increasing by a certain amount?

-Kevin

Unsubscribe: http://mail.python.org/mailman/options/python-dev/jacobs%40bioinformed.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20080621/f0126b1a/attachment.htm>

More information about the Python-Dev mailing list