Yes. Just –in-time releaseing of objects is much preferable to delayed release. They tend to be in the cache, the individual runs of releases are smaller and have less of an individual impact. a gc.collect() cycle visits a large amount of objects that it won‘t release causing cache thrashing. There is a reason we disabled ‚gc‘, and it is simply because we get lower cpu and smoother execution. K
From: daniel.stutzb...@gmail.com [mailto:daniel.stutzb...@gmail.com] On Behalf Of Daniel Stutzbach Sent: 8. desember 2009 15:04 To: Maciej Fijalkowski Cc: Kristján Valur Jónsson; python-dev@python.org Subject: Re: [Python-Dev] recursive closures - reference leak 2009/12/8 Maciej Fijalkowski <fij...@gmail.com<mailto:fij...@gmail.com>> Note that disabling gc does not mean that you will not have unpredictable pauses. Consider for example that if you loose a reference to a very long chain of objects, you can have arbitrarily many frees being called before anything else can happen. That strikes me as a *predictable* long pause. --
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
