[Python-Dev] Python 2.6a2 execution times with various compilers
Jeroen Ruigrok van der Werven
asmodai at in-nomine.org
Sat Apr 12 20:09:36 CEST 2008
I did some more tests concentrating on GCC, partly based on the feedback I
got, results at
http://www.in-nomine.org/2008/04/12/python-26-compiler-options-results/
Executive summary: Python needs to be compiled with -O2 or -O3. Not doing
so, no optimization level, results with GCC 4.2.1 in a doubling of execution
time. Using just -O1 is still ~15% slower than using -O2.
Using -mtune=native -march=native can shave of 0,1/0,2 seconds, but
otherwise I did not find much difference in using having march or mfpmath
present.
Profile-guided optimization did not help much, as might be expected, it
pushed about the same kind of optimization as the mtune/march combination.
--
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
All know that the drop merges into the ocean but few know that the ocean
merges into the drop.
More information about the Python-Dev
mailing list