This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients docs@python, flox, lemburg, pitrou, python-dev, vstinner
Date 2016-09-13.19:27:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473794840.69.0.316221750505.issue15369@psf.upfronthosting.co.za>
In-reply-to
Content
Please add notes to the Tools/README pointing users to the performance suite.

I'd also like to request that you reword this dismissive line in the performance package's readme:

"""
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.
"""

I suppose this was taken from the Unladden Swallow list of benchmarks and completely misses the point of what pybench is all about: it's a benchmark to run performance tests for individual parts of CPython's VM implementation. It never was intended to be representative. The main purpose is to be able to tell whether an optimization in CPython has an impact on individual areas of the interpreter or not.

Thanks.
History
Date User Action Args
2016-09-13 19:27:20lemburgsetrecipients: + lemburg, pitrou, vstinner, flox, docs@python, python-dev
2016-09-13 19:27:20lemburgsetmessageid: <1473794840.69.0.316221750505.issue15369@psf.upfronthosting.co.za>
2016-09-13 19:27:20lemburglinkissue15369 messages
2016-09-13 19:27:20lemburgcreate