________________________________________________________________________PYBENCH - A Python Benchmark Suite________________________________________________________________________Extendable suite of of low-level benchmarks for measuringthe performance of the Python implementation(interpreter, compiler or VM).pybench is a collection of tests that provides a standardized way tomeasure the performance of Python implementations. It takes a veryclose look at different aspects of Python programs and let's youdecide which factors are more important to you than others, ratherthan wrapping everything up in one number, like the other performancetests do (e.g. pystone which is included in the Python StandardLibrary).pybench has been used in the past by several Python developers totrack down performance bottlenecks or to demonstrate the impact ofoptimizations and new features in Python.The command line interface for pybench is the file pybench.py. Runthis script with option '--help' to get a listing of the possibleoptions. Without options, pybench will simply execute the benchmarkand then print out a report to stdout.Micro-Manual------------Run 'pybench.py -h' to see the help screen. Run 'pybench.py' to runthe benchmark suite using default settings and 'pybench.py -f <file>'to have it store the results in a file too.It is usually a good idea to run pybench.py multiple times to seewhether the environment, timers and benchmark run-times are suitablefor doing benchmark tests.You can use the comparison feature of pybench.py ('pybench.py -c<file>') to check how well the system behaves in comparison to areference run.If the differences are well below 10% for each test, then you have asystem that is good for doing benchmark testings. Of you get randomdifferences of more than 10% or significant differences between thevalues for minimum and average time, then you likely have somebackground processes running which cause the readings to becomeinconsistent. Examples include: web-browsers, email clients, RSSreaders, music players, backup programs, etc.If you are only interested in a few tests of the whole suite, you canuse the filtering option, e.g. 'pybench.py -t string' will onlyrun/show the tests that have 'string' in their name.This is the current output of pybench.py --help:"""------------------------------------------------------------------------PYBENCH - a benchmark test suite for Python interpreters/compilers.------------------------------------------------------------------------Synopsis:pybench.py [option] files...Options and default settings:-n arg number of rounds (10)-f arg save benchmark to file arg ()-c arg compare benchmark with the one in file arg ()-s arg show benchmark in file arg, then exit ()-w arg set warp factor to arg (10)-t arg run only tests with names matching arg ()-C arg set the number of calibration runs to arg (20)-d hide noise in comparisons (0)-v verbose output (not recommended) (0)--with-gc enable garbage collection (0)--with-syscheck use default sys check interval (0)--timer arg use given timer (time.time)-h show this help text--help show this help text--debug enable debugging--copyright show copyright--examples show examples of usageVersion:2.0The normal operation is to run the suite and display theresults. Use -f to save them for later reuse or comparisons.Available timers:time.timetime.clocksystimes.processtimeExamples:python2.1 pybench.py -f p21.pybenchpython2.5 pybench.py -f p25.pybenchpython pybench.py -s p25.pybench -c p21.pybench"""License-------See LICENSE file.Sample output-------------"""-------------------------------------------------------------------------------PYBENCH 2.0-------------------------------------------------------------------------------* using Python 2.4.2* disabled garbage collection* system check interval set to maximum: 2147483647* using timer: time.timeCalibrating tests. Please wait...Running 10 round(s) of the suite at warp factor 10:* Round 1 done in 6.388 seconds.* Round 2 done in 6.485 seconds.* Round 3 done in 6.786 seconds....* Round 10 done in 6.546 seconds.-------------------------------------------------------------------------------Benchmark: 2006年06月12日 12:09:25-------------------------------------------------------------------------------Rounds: 10Warp: 10Timer: time.timeMachine Details:Platform ID: Linux-2.6.8-24.19-default-x86_64-with-SuSE-9.2-x86-64Processor: x86_64Python:Executable: /usr/local/bin/pythonVersion: 2.4.2Compiler: GCC 3.3.4 (pre 3.3.5 20040809)Bits: 64bitBuild: Oct 1 2005 15:24:35 (#1)Unicode: UCS2Test minimum average operation overhead-------------------------------------------------------------------------------BuiltinFunctionCalls: 126ms 145ms 0.28us 0.274msBuiltinMethodLookup: 124ms 130ms 0.12us 0.316msCompareFloats: 109ms 110ms 0.09us 0.361msCompareFloatsIntegers: 100ms 104ms 0.12us 0.271msCompareIntegers: 137ms 138ms 0.08us 0.542msCompareInternedStrings: 124ms 127ms 0.08us 1.367msCompareLongs: 100ms 104ms 0.10us 0.316msCompareStrings: 111ms 115ms 0.12us 0.929msCompareUnicode: 108ms 128ms 0.17us 0.693msConcatStrings: 142ms 155ms 0.31us 0.562msConcatUnicode: 119ms 127ms 0.42us 0.384msCreateInstances: 123ms 128ms 1.14us 0.367msCreateNewInstances: 121ms 126ms 1.49us 0.335msCreateStringsWithConcat: 130ms 135ms 0.14us 0.916msCreateUnicodeWithConcat: 130ms 135ms 0.34us 0.361msDictCreation: 108ms 109ms 0.27us 0.361msDictWithFloatKeys: 149ms 153ms 0.17us 0.678msDictWithIntegerKeys: 124ms 126ms 0.11us 0.915msDictWithStringKeys: 114ms 117ms 0.10us 0.905msForLoops: 110ms 111ms 4.46us 0.063msIfThenElse: 118ms 119ms 0.09us 0.685msListSlicing: 116ms 120ms 8.59us 0.103msNestedForLoops: 125ms 137ms 0.09us 0.019msNormalClassAttribute: 124ms 136ms 0.11us 0.457msNormalInstanceAttribute: 110ms 117ms 0.10us 0.454msPythonFunctionCalls: 107ms 113ms 0.34us 0.271msPythonMethodCalls: 140ms 149ms 0.66us 0.141msRecursion: 156ms 166ms 3.32us 0.452msSecondImport: 112ms 118ms 1.18us 0.180msSecondPackageImport: 118ms 127ms 1.27us 0.180msSecondSubmoduleImport: 140ms 151ms 1.51us 0.180msSimpleComplexArithmetic: 128ms 139ms 0.16us 0.361msSimpleDictManipulation: 134ms 136ms 0.11us 0.452msSimpleFloatArithmetic: 110ms 113ms 0.09us 0.571msSimpleIntFloatArithmetic: 106ms 111ms 0.08us 0.548msSimpleIntegerArithmetic: 106ms 109ms 0.08us 0.544msSimpleListManipulation: 103ms 113ms 0.10us 0.587msSimpleLongArithmetic: 112ms 118ms 0.18us 0.271msSmallLists: 105ms 116ms 0.17us 0.366msSmallTuples: 108ms 128ms 0.24us 0.406msSpecialClassAttribute: 119ms 136ms 0.11us 0.453msSpecialInstanceAttribute: 143ms 155ms 0.13us 0.454msStringMappings: 115ms 121ms 0.48us 0.405msStringPredicates: 120ms 129ms 0.18us 2.064msStringSlicing: 111ms 127ms 0.23us 0.781msTryExcept: 125ms 126ms 0.06us 0.681msTryRaiseExcept: 133ms 137ms 2.14us 0.361msTupleSlicing: 117ms 120ms 0.46us 0.066msUnicodeMappings: 156ms 160ms 4.44us 0.429msUnicodePredicates: 117ms 121ms 0.22us 2.487msUnicodeProperties: 115ms 153ms 0.38us 2.070msUnicodeSlicing: 126ms 129ms 0.26us 0.689ms-------------------------------------------------------------------------------Totals: 6283ms 6673ms"""________________________________________________________________________Writing New Tests________________________________________________________________________pybench tests are simple modules defining one or more pybench.Testsubclasses.Writing a test essentially boils down to providing two methods:.test() which runs .rounds number of .operations test operations eachand .calibrate() which does the same except that it doesn't actuallyexecute the operations.Here's an example:------------------from pybench import Testclass IntegerCounting(Test):# Version number of the test as float (x.yy); this is important# for comparisons of benchmark runs - tests with unequal version# number will not get compared.version = 1.0# The number of abstract operations done in each round of the# test. An operation is the basic unit of what you want to# measure. The benchmark will output the amount of run-time per# operation. Note that in order to raise the measured timings# significantly above noise level, it is often required to repeat# sets of operations more than once per test round. The measured# overhead per test round should be less than 1 second.operations = 20# Number of rounds to execute per test run. This should be# adjusted to a figure that results in a test run-time of between# 1-2 seconds (at warp 1).rounds = 100000def test(self):""" Run the test.The test needs to run self.rounds executingself.operations number of operations each."""# Init the testa = 1# Run test rounds## NOTE: Use xrange() for all test loops unless you want to face# a 20MB process !#for i in xrange(self.rounds):# Repeat the operations per round to raise the run-time# per operation significantly above the noise level of the# for-loop overhead.# Execute 20 operations (a += 1):a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1a += 1def calibrate(self):""" Calibrate the test.This method should execute everything that is needed tosetup and run the test - except for the actual operationsthat you intend to measure. pybench uses this method tomeasure the test implementation overhead."""# Init the testa = 1# Run test rounds (without actually doing any operation)for i in xrange(self.rounds):# Skip the actual execution of the operations, since we# only want to measure the test's administration overhead.passRegistering a new test module-----------------------------To register a test module with pybench, the classes need to beimported into the pybench.Setup module. pybench will then scan all thesymbols defined in that module for subclasses of pybench.Test andautomatically add them to the benchmark suite.Breaking Comparability----------------------If a change is made to any individual test that means it is nolonger strictly comparable with previous runs, the '.version' classvariable should be updated. Therefafter, comparisons with previousversions of the test will list as "n/a" to reflect the change.Version History---------------2.0: rewrote parts of pybench which resulted in more repeatabletimings:- made timer a parameter- changed the platform default timer to use high-resolutiontimers rather than process timers (which have a much lowerresolution)- added option to select timer- added process time timer (using systimes.py)- changed to use min() as timing estimator (averageis still taken as well to provide an idea of the difference)- garbage collection is turned off per default- sys check interval is set to the highest possible value- calibration is now a separate step and done usinga different strategy that allows measuring the testoverhead more accurately- modified the tests to each give a run-time of between100-200ms using warp 10- changed default warp factor to 10 (from 20)- compared results with timeit.py and confirmed measurements- bumped all test versions to 2.0- updated platform.py to the latest version- changed the output format a bit to make it looknicer- refactored the APIs somewhat1.3+: Steve Holden added the NewInstances test and the filteringoption during the NeedForSpeed sprint; this also triggered a longdiscussion on how to improve benchmark timing and finallyresulted in the release of 2.01.3: initial checkin into the Python SVN repositoryHave fun,--Marc-Andre Lemburgmal@lemburg.com
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。