This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients christian.heimes, gvanrossum, loewis, matthiastroffaes, pitrou, r.david.murray, rhettinger, skip.montanaro
Date 2009-08-16.17:08:03
SpamBayes Score 1.0488139e-07
Marked as misclassified No
Message-id <1250442485.27.0.00434473336065.issue6695@psf.upfronthosting.co.za>
In-reply-to
Content
I still stand by my suggestion to free memory as a side effect of
garbage collection. It may well be that an application will start
re-allocating blocks that soon end up in the free list again. OTOH, it
may also be that releasing those free lists, along with the freeing that
the GC just did, can cause arenas to become completely free, and thus be
returned to the operating system. Users really really want Python to
return memory to the operating system whenever possible, and on its own;
those free lists can block memory from being returned, more or less
unreasonably.

So unless it can be demonstrated (preferably in a realistic application)
that clearing the free lists has a measurable negative impact, I propose
to keep things the way they are.

IMO, it would be best if we could eliminate the freelists altogether.
History
Date User Action Args
2009-08-16 17:08:05loewissetrecipients: + loewis, gvanrossum, skip.montanaro, rhettinger, pitrou, christian.heimes, r.david.murray, matthiastroffaes
2009-08-16 17:08:05loewissetmessageid: <1250442485.27.0.00434473336065.issue6695@psf.upfronthosting.co.za>
2009-08-16 17:08:03loewislinkissue6695 messages
2009-08-16 17:08:03loewiscreate