Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-December/084398.html below:

[Python-Dev] Calling the GC less often when there are lots of long-lived objects

• Previous message: [Python-Dev] Calling the GC less often when there are lots of long-lived objects
• Next message: [Python-Dev] Calling the GC less often when there are lots of long-lived objects
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Christian Heimes <lists <at> cheimes.de> writes:
> 
> Is it reasonable to implement multiple policies so the user can switch
> between them? Or is the new algorithm superior in all cases?

We could let the user configure the threshold between the old policy and the new
policy. Currently it is hard-wired to a value of 10000 (that is, 10000
long-lived objects tracked by the GC).

• Previous message: [Python-Dev] Calling the GC less often when there are lots of long-lived objects
• Next message: [Python-Dev] Calling the GC less often when there are lots of long-lived objects
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4