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 giampaolo.rodola
Recipients christian.heimes, felipecruz, giampaolo.rodola, gvanrossum, meador.inge, neologix, pitrou, python-dev, rhettinger, rosslagerwall, sbt, vstinner, yselivanov
Date 2015-02-15.21:31:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1424035915.31.0.156723174627.issue18932@psf.upfronthosting.co.za>
In-reply-to
Content
Attached is a patch (for epoll only) which updates the SelectorKey. This introduces a considerable slowdown compared to my first patch:

no patch:    16.2 usec per loop
your patch:  12.4 usec per loop
my patch:    10.9 usec per loop
first patch: 3.07 usec per loop

The culprit is the new nameduple's _replace() call. It's a shame a single line adds such a great slowdown. I think it makes sense to investigate whether we can introduce a faster replace mechanism for namedtuple.
History
Date User Action Args
2015-02-15 21:31:55giampaolo.rodolasetrecipients: + giampaolo.rodola, gvanrossum, rhettinger, pitrou, vstinner, christian.heimes, meador.inge, neologix, rosslagerwall, python-dev, sbt, felipecruz, yselivanov
2015-02-15 21:31:55giampaolo.rodolasetmessageid: <1424035915.31.0.156723174627.issue18932@psf.upfronthosting.co.za>
2015-02-15 21:31:55giampaolo.rodolalinkissue18932 messages
2015-02-15 21:31:55giampaolo.rodolacreate