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 pitrou
Recipients Yury.Selivanov, casevh, josh.r, lemburg, mark.dickinson, pitrou, rhettinger, serhiy.storchaka, skrah, vstinner, yselivanov, zbyrne
Date 2016-02-04.22:55:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454626542.04.0.269410613953.issue21955@psf.upfronthosting.co.za>
In-reply-to
Content
People should stop getting hung up about benchmarks numbers and instead should first think about what they are trying to *achieve*. FP performance in pure Python does not seem like an important goal in itself. Also, some benchmarks may show variations which are randomly correlated with a patch (e.g. before of different code placement by the compiler interfering with instruction cache wayness). It is important not to block a patch because some random benchmark on some random machine shows an unexpected slowdown.

That said, both of Serhiy's patches are probably ok IMO.
History
Date User Action Args
2016-02-04 22:55:42pitrousetrecipients: + pitrou, lemburg, rhettinger, mark.dickinson, vstinner, casevh, skrah, Yury.Selivanov, serhiy.storchaka, yselivanov, josh.r, zbyrne
2016-02-04 22:55:42pitrousetmessageid: <1454626542.04.0.269410613953.issue21955@psf.upfronthosting.co.za>
2016-02-04 22:55:42pitroulinkissue21955 messages
2016-02-04 22:55:41pitroucreate