[Python-Dev] PyGC_Collect ignores state of enabled (original) (raw)

Łukasz Langa lukasz at langa.pl
Mon May 9 22:13:48 EDT 2016

Is this deliberate? Could we change it for 3.6 so PyGC_Collect does take enabled into account?

Context: we’re experimenting with disabling the gc entirely for some workloads because it doesn’t fare too well with Copy-on-Write on Linux. What ends up happening is that disabling the gc actually drops memory usage significantly if you’re using hundreds of the same processes on one box :-)

However, because of PyGC_Collect() called in Py_Finalize(), during interpreter shutdown the collection is done anyway, Linux does CoW and the memory usage spikes. Which is ironic on process shutdown.

-- Lukasz Langa | Facebook Production Engineer | The Ministry of Silly Walks (+1) 650-681-7811

-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20160509/ad72912f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://mail.python.org/pipermail/python-dev/attachments/20160509/ad72912f/attachment.sig>

More information about the Python-Dev mailing list