Benchmark Results for Python Default 2015-07-24
Hi Internals, This is the first message from Intel's language optimization team. We would like to provide the Python internals developer community with a daily service which will monitor latest committed patches performance regressions against well known workloads. Our aim is to run a multitude of workloads as well as real-life scenarios which the community considers relevant. The service will send daily bulletins containing latest measurements for daily variations and variations against latest stable release run on our Intel-enabled servers. The community's feedback is very important for us. For any questions, comments or suggestions you can also contact us on our mailing list lp@lists.01.org. You can also check our website: https://www.01.org/lp Results for project python_default-nightly, build date 2015-07-24 09:02:02 commit: 3bbd0cbfe836511dd3e05fcc30ffb5bdbfe686ea revision date: 2015-07-24 07:43:44 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 Note: Baseline results were generated using release v3.4.3, with hash b4cbecbc0781e89a309d03b60a1f75f8499250e6 from 2015-02-25 12:15:33+00:00 -------------------------------------------------------------------------------- benchmark unit change since change since last run v3.4.3 -------------------------------------------------------------------------------- :-) django_v2 sec 1.12735% 7.47953% :-( pybench sec -0.53822% -2.40216% :-( regex_v8 sec 0.61774% -2.32010% :-| nbody sec 1.75860% -0.76206% :-) json_dump_v2 sec 2.13422% -0.56930% 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. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. This document may contain information on products, services and/or processes in development. Contact your Intel representative to obtain the latest forecast, schedule, specifications and roadmaps. The products and services described may contain defects or errors known as errata which may cause deviations from published specifications. Current characterized errata are available on request. (C) 2015 Intel Corporation.
On 24.07.15 15:34, lp_benchmark_robot wrote:
Hi Internals,
This is the first message from Intel's language optimization team. We would like to provide the Python internals developer community with a daily service which will monitor latest committed patches performance regressions against well known workloads. Our aim is to run a multitude of workloads as well as real-life scenarios which the community considers relevant. The service will send daily bulletins containing latest measurements for daily variations and variations against latest stable release run on our Intel-enabled servers.
The community's feedback is very important for us. For any questions, comments or suggestions you can also contact us on our mailing list lp@lists.01.org. You can also check our website: https://www.01.org/lp
It is cool! Thank you, it whats we need. But perhaps it would be better to post these reports on python-checkins@python.org instead of Python-Dev list, with Reply-To set to python-dev@python.org.
On 24 July 2015 at 23:55, Serhiy Storchaka <storchaka@gmail.com> wrote:
On 24.07.15 15:34, lp_benchmark_robot wrote:
The community's feedback is very important for us. For any questions, comments or suggestions you can also contact us on our mailing list lp@lists.01.org. You can also check our website: https://www.01.org/lp
It is cool! Thank you, it whats we need.
Indeed!
But perhaps it would be better to post these reports on python-checkins@python.org instead of Python-Dev list, with Reply-To set to python-dev@python.org.
Aye, python-checkins is a better option for automated daily posts. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
Should we discuss of these are the benchmarks we want daily reports on (you can see what the benchmark suite has at https://hg.python.org/benchmarks/file/2979f5ce6a0c/perf.py#l2243 )? I personally would prefer dropping pybench and replacing it with a startup measurement. On Fri, Jul 24, 2015, 07:23 Nick Coghlan <ncoghlan@gmail.com> wrote:
On 24 July 2015 at 23:55, Serhiy Storchaka <storchaka@gmail.com> wrote:
On 24.07.15 15:34, lp_benchmark_robot wrote:
The community's feedback is very important for us. For any questions, comments or suggestions you can also contact us on our mailing list lp@lists.01.org. You can also check our website: https://www.01.org/lp
It is cool! Thank you, it whats we need.
Indeed!
But perhaps it would be better to post these reports on python-checkins@python.org instead of Python-Dev list, with Reply-To set to python-dev@python.org.
Aye, python-checkins is a better option for automated daily posts.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org
Brett Cannon <brett <at> python.org> writes:
Should we discuss of these are the benchmarks we want daily reports on
(you can see what the benchmark suite has at https://hg.python.org/benchmarks/file/2979f5ce6a0c/perf.py#l2243 )? I personally would prefer dropping pybench and replacing it with a startup measurement.
On Fri, Jul 24, 2015, 07:23 Nick Coghlan <ncoghlan <at> gmail.com> wrote:
On 24 July 2015 at 23:55, Serhiy Storchaka <storchaka <at> gmail.com>
On 24.07.15 15:34, lp_benchmark_robot wrote:
The community's feedback is very important for us. For any questions, comments or suggestions you can also contact us on our mailing list lp <at> lists.01.org. You can also check our website: https://www.01.org/lp
It is cool! Thank you, it whats we need. Indeed! But perhaps it would be better to post these reports on python-checkins <at> python.org instead of Python-Dev list, with Reply- To set to python-dev <at> python.org. Aye, python-checkins is a better option for automated daily posts. Cheers, Nick. -- Nick Coghlan | ncoghlan <at> gmail.com | Brisbane, Australia
Python-Dev mailing listPython-Dev <at>
Unsubscribe: https://mail.python.org/mailman/options/python- dev/brett%40python.org
<div> <p dir="ltr">Should we discuss of these are the benchmarks we want daily reports on (you can see what the benchmark suite has at <br><a
<br><div class="gmail_quote"> <div dir="ltr">On Fri, Jul 24, 2015, 07:23 Nick Coghlan <<a
</div> <blockquote class="gmail_quote">On 24 July 2015 at 23:55, Serhiy Storchaka <<a href="mailto:storchaka <at> gmail.com" target="_blank">storchaka <at> gmail.com</a>> wrote:<br>
On 24.07.15 15:34, lp_benchmark_robot wrote:<br>
The community's feedback is very important for us. For any questions,<br> comments or suggestions you can also contact us on our mailing
<a href="mailto:lp <at> lists.01.org" target="_blank">lp <at>
<br> It is cool! Thank you, it whats we need.<br><br> Indeed!<br><br> But perhaps it would be better to post these reports on<br> <a href="mailto:python-checkins <at> python.org" target="_blank">python-checkins <at> python.org</a> instead of Python-Dev
<a href="mailto:python-dev <at> python.org" target="_blank">python- dev <at> python.org</a>.<br><br> Aye, python-checkins is a better option for automated daily posts.<br><br> Cheers,<br> Nick.<br><br> --<br> Nick Coghlan | <a href="mailto:ncoghlan <at> gmail.com" target="_blank">ncoghlan <at> gmail.com</a> | Brisbane, Australia<br> _______________________________________________<br> Python-Dev mailing list<br><a href="mailto:Python-Dev <at> python.org" target="_blank">Python-Dev <at> python.org</a><br><a
wrote: python.orghttps://mail.python.org/mailman/listinfo/python-dev href="https://hg.python.org/benchmarks/file/2979f5ce6a0c/perf.py#l2243">http s://hg.python.org/benchmarks/file/2979f5ce6a0c/perf.py#l2243</a> )? I personally would prefer dropping pybench and replacing it with a startup measurement.</p> href="mailto:ncoghlan <at> gmail.com">ncoghlan <at> gmail.com</a>> wrote: <br> list<br> lists.01.org</a>. You can also check our website: <a href="https://www.01.org/lp" rel="noreferrer" target="_blank">https://www.01.org/lp</a><br> list, with Reply-To set to<br> href="https://mail.python.org/mailman/listinfo/python-dev" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python- dev/brett%40python.org" rel="noreferrer" target="_blank">https://mail.python.org/mailman/options/python- dev/brett%40python.org</a><br> </blockquote> </div> </div>
Thank you for your feedback! We value the community’s input and we would like to provide the most relevant results in our automatic measurements. Regarding the startup benchmarks, could you tell us which one you think is the most useful to be included in the daily report ("normal_startup", "startup_nosite")? Regards !
On Wed, Jul 29, 2015 at 9:40 AM Catalin G. Manciu < catalin.gabriel.manciu@intel.com> [SNIP -- stuff came back as visible HTML; hopefully I didn't miss something]
Thank you for your feedback! We value the community’s input and we would like to provide the most relevant results in our automatic measurements. Regarding the startup benchmarks, could you tell us which one you think is the most useful to be included in the daily report ("normal_startup", "startup_nosite")?
I personally think normal_startup is best as that's how people probably typically launch Python.
Hi, I don't know if it's related but at EuroPython at saw a new website which can also help: http://pybenchmarks.org/ Victor
účastníci (6)
-
Brett Cannon -
Catalin G. Manciu -
lp_benchmark_robot -
Nick Coghlan -
Serhiy Storchaka -
Victor Stinner