➜

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 ncoghlan
Recipients Arfrever, christian.heimes, ncoghlan, neologix, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2013-11-16.10:24:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384597479.7.0.380566361319.issue19183@psf.upfronthosting.co.za>
In-reply-to
Content 
Thanks - are those numbers with the current feature branch, and hence no small string optimization?

To be completely clear, I'm happy to accept a performance penalty to fix the hash algorithm. I'd just like to know exactly how big a penalty I'm accepting, and whether taking advantage of the small string optimization makes it measurably smaller.
History
Date User Action Args
2013-11-16 10:24:39ncoghlansetrecipients: + ncoghlan, pitrou, vstinner, christian.heimes, Arfrever, neologix, python-dev, serhiy.storchaka
2013-11-16 10:24:39ncoghlansetmessageid: <1384597479.7.0.380566361319.issue19183@psf.upfronthosting.co.za>
2013-11-16 10:24:39ncoghlanlinkissue19183 messages
2013-11-16 10:24:39ncoghlancreate