[Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers) (original) (raw)
Hynek Schlawack hs at ox.cx
Sun Oct 28 14:25:40 CET 2012
- Previous message: [Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers)
- Next message: [Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 28.10.2012 um 12:11 schrieb Antoine Pitrou <solipsis at pitrou.net>:
One word: profile.
Looking at stat counts alone rather than measuring the total time spent in all types of system calls from strace and profiling is not really useful. ;) Agreed, but I can't seem to cope properly with gprof. Any suggestion?
http://oprofile.sourceforge.net/news/ http://valgrind.org/docs/manual/cl-manual.html
Are both useful. gprof is virtually useless.
- Previous message: [Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers)
- Next message: [Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]