[Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers) (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Sat Oct 27 22:59:32 CEST 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 ]
On Sat, 27 Oct 2012 21:40:26 +0100 Mark Shannon <mark at hotpy.org> wrote:
On 27/10/12 20:21, Antoine Pitrou wrote: > > It would be interesting to know where the module import time gets > spent, on a lower level. My gut feeling is that execution of Python > module code is the main contributor.
I suspect that stating and loading the .pyc files is responsible for most of the overhead. PyRun starts up quite a lot faster thanks to embedding all the modules in the executable: http://www.egenix.com/products/python/PyRun/
Any numbers?
Regards
Antoine.
- 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 ]