On Sat, Jun 21, 2008 at 11:20 AM, "Martin v. Löwis" <[EMAIL PROTECTED]> 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 >
_______________________________________________ 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
