Hi,
On Wed, May 29, 2013 at 9:00 PM, Eric Snow ericsnowcurren...@gmail.com wrote:
...
What would be important to say in the devguide regarding Python
performance and testing it?
In the devguide I would only add information that are specific to
benchmarking the interpreter.
A separate
Date: Wed, 29 May 2013 12:00:44 -0600
From: ericsnowcurren...@gmail.com
To: python-dev@python.org
Subject: [Python-Dev] performance testing recommendations in devguide
The devguide doesn't have anything on performance testing that I could
find. We do
Hi,
On Wed, 29 May 2013 12:00:44 -0600
Eric Snow ericsnowcurren...@gmail.com wrote:
The devguide doesn't have anything on performance testing that I could
find.
See http://bugs.python.org/issue17449
Tools I'm aware of:
* pybench (relatively limited in real-world usefulness)
* timeit
Hi,
On Wed, 29 May 2013 21:59:21 +0300
Carlos Nepomuceno carlosnepomuc...@outlook.com wrote:
[1] pybench - run the standard Python PyBench benchmark suite. This is
considered
an unreliable, unrepresentative benchmark; do not base decisions
off it. It is included only for completeness.
On Wed, May 29, 2013 at 9:19 PM, Antoine Pitrou solip...@pitrou.net wrote:
Hi,
On Wed, 29 May 2013 21:59:21 +0300
Carlos Nepomuceno carlosnepomuc...@outlook.com wrote:
[1] pybench - run the standard Python PyBench benchmark suite. This is
considered
an unreliable, unrepresentative
On 29.05.2013 21:19, Antoine Pitrou wrote:
Hi,
On Wed, 29 May 2013 21:59:21 +0300
Carlos Nepomuceno carlosnepomuc...@outlook.com wrote:
[1] pybench - run the standard Python PyBench benchmark suite. This is
considered
an unreliable, unrepresentative benchmark; do not base decisions
29.05.13 21:00, Eric Snow написав(ла):
Critically sensitive performance subjects
* interpreter start-up time
* module import overhead
* attribute lookup overhead (including MRO traversal)
* function call overhead
* instance creation overhead
* dict performance (the underlying namespace type)
*
