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 gregory.p.smith
Recipients christian.heimes, gregory.p.smith, gvanrossum, loewis, matthiastroffaes, pitrou, r.david.murray, rhettinger, skip.montanaro
Date 2009-08-16.18:23:47
SpamBayes Score 0.0002720526
Marked as misclassified No
Message-id <1250447028.51.0.31108745184.issue6695@psf.upfronthosting.co.za>
In-reply-to
Content
+1 on the PyXXX_ClearFreeList patch and calling them from gc.collect()
as is done with the others.

I agree with Guido, don't add a tp_free_list slot as the common case
would be NULL.

Regarding gc clearing freelists: I agree with Antoine and Martin. 
Clearing free lists in the highest generation of GC is a very good
thing.  Rebuilding them infrequently should not have a significant
performance impact and makes long running python jobs better behaved by
releasing more memory when possible.
History
Date User Action Args
2009-08-16 18:23:48gregory.p.smithsetrecipients: + gregory.p.smith, gvanrossum, loewis, skip.montanaro, rhettinger, pitrou, christian.heimes, r.david.murray, matthiastroffaes
2009-08-16 18:23:48gregory.p.smithsetmessageid: <1250447028.51.0.31108745184.issue6695@psf.upfronthosting.co.za>
2009-08-16 18:23:47gregory.p.smithlinkissue6695 messages
2009-08-16 18:23:47gregory.p.smithcreate