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 tim.peters
Recipients Dmitry Rubanovich, methane, pitrou, rhettinger, serhiy.storchaka, tim.peters, xgdomingo, xiang.zhang
Date 2017-06-26.05:15:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498454115.2.0.8344006126.issue29304@psf.upfronthosting.co.za>
In-reply-to
Content
I suggest reading the thread I started here[1] before pursuing this:  it looks very likely that the entire collision resolution scheme should be replaced with one of the "double hashing" ones given there, a bona fide algorithmic improvement for small tables and pathological key sets.  Whether it actually runs faster remains a mystery ;-)  The loop guts change from a shift, three adds, and a mask (or a multiply, two adds, and a mask) to just one add and a mask.  But the post-first-probe pre-loop setup gets more expensive.

[1] https://mail.python.org/pipermail/python-ideas/2017-June/046143.html
History
Date User Action Args
2017-06-26 05:15:15tim.peterssetrecipients: + tim.peters, rhettinger, pitrou, methane, serhiy.storchaka, xiang.zhang, xgdomingo, Dmitry Rubanovich
2017-06-26 05:15:15tim.peterssetmessageid: <1498454115.2.0.8344006126.issue29304@psf.upfronthosting.co.za>
2017-06-26 05:15:15tim.peterslinkissue29304 messages
2017-06-26 05:15:14tim.peterscreate