[Python-Dev] Program runs in 12s on Python 2.7, but 5s on Python 3.5 -- why so much difference? (original) (raw)
Gregory P. Smith greg at krypto.org
Mon Jul 24 17:03:42 EDT 2017
- Previous message (by thread): [Python-Dev] Program runs in 12s on Python 2.7, but 5s on Python 3.5 -- why so much difference?
- Next message (by thread): [Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Jul 24, 2017 at 1:49 PM Wang, Peter Xihong < peter.xihong.wang at intel.com> wrote:
I believe we have evaluated clang vs gcc before (long time ago), and gcc won at that time.
PGO might have overshadowed impact from computed goto, and thus the latter may no longer be needed.
Computed goto is still needed. PGO does not magically replace it. A PGO build with computed goto is faster than one without computed goto.
... as tested on gcc 4.9 a couple years ago. I doubt that has changed or changes between compilers; PGO and computed goto are different types of optimizations.
-gps -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170724/343fcd3b/attachment.html>
- Previous message (by thread): [Python-Dev] Program runs in 12s on Python 2.7, but 5s on Python 3.5 -- why so much difference?
- Next message (by thread): [Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]