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 mirabilos
Recipients Ramchandra Apte, alanh, christian.heimes, ezio.melotti, jcea, mirabilos, pitrou, serhiy.storchaka, skrah, trent
Date 2013-05-10.16:28:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368203337.08.0.569020853788.issue17237@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine: precisely.

Serhiy: sure. The times are now in msec per loop.
I did three subsequent runs, so the second and
third tuple are cache-warm.

Without assert: (89,88), (87,87), (89,86)
Without block : (79,78), (78,78), (79,78)

And in a second run:

Without assert: (87,88), (87,88), (92,87)
Without block : (111,91), (78,85), (79,79)

This means that, again, removing the “optimised”
code speeds up operations (on this particular
slow architecture.
History
Date User Action Args
2013-05-10 16:28:57mirabilossetrecipients: + mirabilos, jcea, pitrou, christian.heimes, trent, ezio.melotti, alanh, skrah, Ramchandra Apte, serhiy.storchaka
2013-05-10 16:28:57mirabilossetmessageid: <1368203337.08.0.569020853788.issue17237@psf.upfronthosting.co.za>
2013-05-10 16:28:57mirabiloslinkissue17237 messages
2013-05-10 16:28:56mirabiloscreate