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 mscuthbert
Recipients mscuthbert, rhettinger, serhiy.storchaka, wolma
Date 2017-09-08.06:25:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504851950.63.0.702770097488.issue26904@psf.upfronthosting.co.za>
In-reply-to
Content
I've tried to get the system to not be slower on small sets by not creating a Counter for less than 60 items, and managed to get within 10% of the speed for small sequences while maintaining the 3-3.6x speedup for big comparisons and testing that the results were unchanged, but the code just became far too unmanageable for such a small function as quick_ratio, with code forking that would be hard to maintain.  

I'll upload the stub of the replacement for quick_ratio for future developments, in case the creation of Counter objects (the bottleneck) ever disappears, in which case this code will be simpler and faster than the current implementation, but until then, I think it's best to close this issue.
History
Date User Action Args
2017-09-08 06:25:50mscuthbertsetrecipients: + mscuthbert, rhettinger, serhiy.storchaka, wolma
2017-09-08 06:25:50mscuthbertsetmessageid: <1504851950.63.0.702770097488.issue26904@psf.upfronthosting.co.za>
2017-09-08 06:25:50mscuthbertlinkissue26904 messages
2017-09-08 06:25:50mscuthbertcreate