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 vstinner
Recipients josh.r, serhiy.storchaka, vstinner, yselivanov
Date 2016-02-02.22:37:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454452654.4.0.615910502389.issue26233@psf.upfronthosting.co.za>
In-reply-to
Content
Serhiy Storchaka: "I'm not sure that it is worth to apply this optimization. The patch adds half a hundred lines of complex code for only 80 ns benefit. On my computer just incrementing an integer takes 100 ns."

Yury Selivanov: "(...) Right, but there are so many other things which contribute to the memory fragmentation.. I doubt that optimizing epoll will make any detectable improvement on that side."

To be honest, I expected better speedup before I ran the benchmark. That's why I repeat that any performance patch must come with a concrete benchmark showing a non-negligible speedup ;-)

I reject my optimization since it doesn't make the code faster.
History
Date User Action Args
2016-02-02 22:37:34vstinnersetrecipients: + vstinner, serhiy.storchaka, yselivanov, josh.r
2016-02-02 22:37:34vstinnersetmessageid: <1454452654.4.0.615910502389.issue26233@psf.upfronthosting.co.za>
2016-02-02 22:37:34vstinnerlinkissue26233 messages
2016-02-02 22:37:34vstinnercreate