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 lemburg
Recipients lemburg, luis@luispedro.org, methane, rhettinger, serhiy.storchaka, terry.reedy, tim.peters, twouters, vstinner
Date 2018-02-17.13:44:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <b553909b-3c5c-3d4d-2cc0-37160e69e460@egenix.com>
In-reply-to <1518869385.42.0.467229070634.issue32846@psf.upfronthosting.co.za>
Content
Reminds of some experiments someone did a while ago as part of the
GIL removal attempts where the ref count integers are all kept in a
separate array. The intent there was to be able to do locking on
a single array rather than on individual decref cells.

This would solve the issue with having to jump around in memory
to decref all objects, but I'm not sure whether the overall win
would be a lot, since deallocation of the memory blocks typically
requires accessing the block itself as well (to update the block
chain list pointers), unless the memory allocator uses some
smart cache local block management as well (I believe that pymalloc
does, but could be wrong).

In any case, this sounds like a fun experiment for a GSoC student.
Perhaps the PSF could donate an AWS EC2 instance with enough RAM to
do the experiments.
History
Date User Action Args
2018-02-17 13:44:57lemburgsetrecipients: + lemburg, tim.peters, twouters, rhettinger, terry.reedy, vstinner, luis@luispedro.org, methane, serhiy.storchaka
2018-02-17 13:44:57lemburglinkissue32846 messages
2018-02-17 13:44:56lemburgcreate