On Sat, Jun 21, 2008 at 11:20 AM, "Martin v. Löwis" <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In general, any solution of the "do GC less often" needs to deal with<br>
cases where lots of garbage gets produced in a short amount of time<br>
(e.g. in a tight loop), and which run out of memory when GC is done less<br>
often.<br>
</blockquote><div><br>
<br>
Idea 1: Allow GC to run automatically no more often than n CPU seconds, n being perhaps 5 or 10.<br>
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.<br>
<br>
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?<br>
<br>
-Kevin<br>
<br>
</div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="Wj3C7c"><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/jacobs%40bioinformed.com" target="_blank">http://mail.python.org/mailman/options/python-dev/jacobs%40bioinformed.com</a><br>
</div></div></blockquote></div><br>