[Python-checkins] BAD Benchmark Results for Python Default 2016-09-23

lp_benchmark_robot at intel.com lp_benchmark_robot at intel.com
Fri Sep 23 09:48:32 EDT 2016


Results for project Python default, build date 2016-09-23 02:00:58 +0000
commit:		15f82b64eee0
previous commit:	e5888f5b9cf8
revision date:	2016-09-23 00:11:53 +0000
environment:	Haswell-EP
	cpu:		Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB
	mem:		128 GB
	os:		CentOS 7.1
	kernel:	Linux 3.10.0-229.4.2.el7.x86_64

Baseline results were generated using release v3.4.3, with hash b4cbecbc0781
from 2015-02-25 12:15:33+00:00

----------------------------------------------------------------------------------
              benchmark   relative   change since   change since   current rev run
                          std_dev*       last run       baseline          with PGO
----------------------------------------------------------------------------------
:-)           django_v2      0.18%         -1.87%          3.79%            14.76%
:-)             pybench      0.12%          0.23%          4.21%             5.57%
:-(            regex_v8      3.83%         -0.08%         -2.13%             4.51%
:-)               nbody      0.27%          0.40%          2.84%             5.71%
:-(        json_dump_v2      0.32%          0.15%         -3.40%             9.25%
:-)      normal_startup      0.45%         -0.79%          3.69%             6.31%
----------------------------------------------------------------------------------

* Relative Standard Deviation (Standard Deviation/Average)

If this is not displayed properly please visit our results page here: http://languagesperformance.intel.com/bad-benchmark-results-for-python-default-2016-09-23/

Note: Benchmark results are measured in seconds.

Subject Label Legend:
Attributes are determined based on the performance evolution of the workloads
compared to the previous measurement iteration.
NEUTRAL: performance did not change by more than 1% for any workload
GOOD: performance improved by more than 1% for at least one workload and there
is no regression greater than 1%
BAD: performance dropped by more than 1% for at least one workload and there is
no improvement greater than 1%
UGLY: performance improved by more than 1% for at least one workload and also
dropped by more than 1% for at least one workload


Our lab does a nightly source pull and build of the Python project and measures
performance changes against the previous stable version and the previous nightly
measurement. This is provided as a service to the community so that quality
issues with current hardware can be identified quickly.

Intel technologies' features and benefits depend on system configuration and may
require enabled hardware, software or service activation. Performance varies
depending on system configuration.


More information about the Python-checkins mailing list