Jim Jewett jimjjewett at gmail.com
Mon Feb 18 22:13:05 CET 2008

• Previous message: [Python-Dev] Small RFEs and the Bug Tracker
• Next message: [Python-Dev] Different float formatting on Windows and Linux
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> A simple way to do this would be to push objects whose
> refcounts had reached 0 onto a list instead of finalizing them
> immediately, and have PyEval_EvalFrameEx periodically swap
> in a new to-delete list and delete the objects on the old one.

Some of the memory management threads discussed something similar to
this, and pointed to IBM papers on Java.  By adding states like
"tenatively finalizable", the cost of using multiple processors was
reduced.

The down side is that objects which could be released (and recycled)
immediately won't be -- which slows down a fair number of real-world
programs that are used to the CPython refcount model.  If the resource
not being immediately released is scarce (such as file handles), it
gets even worse.

-jJ

---

• Previous message: [Python-Dev] Small RFEs and the Bug Tracker
• Next message: [Python-Dev] Different float formatting on Windows and Linux
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list