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 rhettinger
Recipients lemburg, methane, rhettinger, serhiy.storchaka, terry.reedy, tim.peters, twouters, vstinner
Date 2018-02-16.05:02:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1518757335.4.0.467229070634.issue32846@psf.upfronthosting.co.za>
In-reply-to
Content
Random idea:  For some range of array sizes (bigger than L3 cache), there might be a net benefit to sorting L1-sized clumps of pointers before making the Py_DECREF calls.  Possibly, the cost of sorting would be offset by improved memory access patterns.

On the other hand, this might just optimize an artificial benchmark that isn't representative of real code where the data is actually being used.  In that case, the program is already going to have to hop all over memory just to access the referred-to objects.
History
Date User Action Args
2018-02-16 05:02:15rhettingersetrecipients: + rhettinger, lemburg, tim.peters, twouters, terry.reedy, vstinner, methane, serhiy.storchaka
2018-02-16 05:02:15rhettingersetmessageid: <1518757335.4.0.467229070634.issue32846@psf.upfronthosting.co.za>
2018-02-16 05:02:15rhettingerlinkissue32846 messages
2018-02-16 05:02:14rhettingercreate