[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 21:21:39 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 09:20:36 -0400 Brett Cannon <bcannon at gmail.com> wrote:
I did check that markup safe as not installed. It might just be mako doing something silly.
The threads tests are very synthetic. And yes, there are more modules at startup. When was the last to,e we looked at them to make sure we weren't doing needless I ports?
The last time was between 3.2 and 3.3. It will be hard to lower the number of imported modules, given the current semantics (io, importlib, unicode, site.py, sysconfig...). Python 2's view of the world was much simpler (naïve?) in comparison.
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.
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 ]