A RetroSearch Logo

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

Search Query:

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

[Python-Dev] GC Proposal

[Python-Dev] GC ProposalAdam Olsen rhamph at gmail.com
Sun Jun 29 19:12:14 CEST 2008
On Sun, Jun 29, 2008 at 12:59 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> Looks about equivalent, but "survivors" may mean two different things
>> depending on if it removes deleted survivors or not.  Splitting that
>> up, we get this form:
>>
>> old <= survivors * 2.0 + deleted * 1.0
>
> What precisely would be the "deleted" count? If it counts deallocations,
> is it relevant what generation the deallocated object was from?
> If so, how do you determine the generation? If not, wouldn't
>
> while 1:
>  x=[]
>
> trigger a full garbage collection fairly quickly?

"deleted" means deallocated survivors.

I could imagine wanting to move survivors and deleted up to the first
generation, to give a stronger guarantee of how often it'd run, but
that'd require a much smaller deleted factor.


-- 
Adam Olsen, aka Rhamphoryncus
More information about the Python-Dev mailing list

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