A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2009-March/086880.html below:

[Python-Dev] 3.1 performance

[Python-Dev] 3.1 performance [Python-Dev] 3.1 performanceAntoine Pitrou solipsis at pitrou.net
Sat Mar 7 15:07:48 CET 2009
Hello,

Out of curiosity, I timed running the test suite ("./python -m test.regrtest")
in non-debug mode, in both the release30-maint and py3k branches:

* release30-maint got:
302 tests OK.
[...]
165.79user 26.03system 5:01.75elapsed 63%CPU

* py3k got:
304 tests OK.
[...]
113.33user 28.93system 4:06.79elapsed 57%CPU

So, 3.1 is 30% faster in user CPU time, even though it probably has more tests
(because of io-c, ordereddict and importlib). This is on a 64-bit Linux AMD
system, and I got similar results on a 64-bit Linux Core2 system.

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4