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 serhiy.storchaka
Recipients methane, pitrou, serhiy.storchaka
Date 2018-05-22.15:31:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527003072.9.0.682650639539.issue33597@psf.upfronthosting.co.za>
In-reply-to
Content
This is an interesting idea.

The other problem with the garbage collecting is that it modifies the memory of all collectable objects. This leads to deduplicating virtually all memory blocks after the fork, even if these objects are not used in the child.

If gc_refcnt is used only when collecting, what if allocate a linear array for them for that time? This will save less memory (only one word per object in the peak), but avoid modifying the memory of not collected objects (except pointers at the ends of generation lists and neighbors of collected objects).
History
Date User Action Args
2018-05-22 15:31:12serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, methane
2018-05-22 15:31:12serhiy.storchakasetmessageid: <1527003072.9.0.682650639539.issue33597@psf.upfronthosting.co.za>
2018-05-22 15:31:12serhiy.storchakalinkissue33597 messages
2018-05-22 15:31:12serhiy.storchakacreate