>> 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.
So when an object gets deallocated, how do you find out whether it survived a middle collection? > 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. This I don't understand. What is the first generation? Generation 0 (i.e. the youngest objects)? Why would you want to move objects surviving a garbage collection back to the youngest generation? That totally defeats the purpose of generational garbage collection. Also, why would you want to move deleted objects anywhere? Their storage is reclaimed, and they don't occur in any list of objects. Regards, Martin _______________________________________________ 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
