Re: [Python-Dev] Avoiding CPython performance regressions

Hi all, Spending an hour with "hg bisect" is a good way to figure out some of the worst speed regressions that occurred in the early days of 2.7 (which are still not fixed now). Here's my favorite's pick: * be4bec689de3 made bm_mako 15% slower, and spitfire_cstringio even much more *

Re: [Python-Dev] Avoiding CPython performance regressions

t;, Stefan A Popa <stefan.a.p...@intel.com<mailto:stefan.a.p...@intel.com>> Subject: Re: [Python-Dev] Avoiding CPython performance regressions From: Fabio Zadrozny <fabi...@gmail.com<mailto:fabi...@gmail.com>> Date: Tuesday, December 1, 2015 at 1:36 AM To: David Stewar

Re: [Python-Dev] Avoiding CPython performance regressions

You may also be interested in a project I've been working on, airspeed velocity, which will automatically benchmark historical versions of a git or hg repo. http://github.com/spacetelescope/asv astropy, scipy, numpy and dask are already using it. Cheers, Mike

Re: [Python-Dev] Avoiding CPython performance regressions

On 12/1/15, 11:38 AM, "Maciej Fijalkowski" wrote: >On Tue, Dec 1, 2015 at 9:04 PM, Stewart, David C > wrote: >> >> Part of the reason that I monitor ssbench so closely on Python 2 is that >> Swift is a major element in cloud computing (and

Re: [Python-Dev] Avoiding CPython performance regressions

at 1:36 AM > To: David Stewart > <david.c.stew...@intel.com<mailto:david.c.stew...@intel.com>> > Cc: "R. David Murray" <rdmur...@bitdance.com<mailto:rdmur...@bitdance.com>>, > "python-dev@python.org<mailto:python-dev@python.org>" > <

Re: [Python-Dev] Avoiding CPython performance regressions

On 12/1/15, 10:56 AM, "Maciej Fijalkowski" wrote: >Hi David. > >Any reason you run a tiny tiny subset of benchmarks? We could always run more. There are so many in the full set in https://hg.python.org/benchmarks/ with such divergent results that it seems hard to see the

Re: [Python-Dev] Avoiding CPython performance regressions

On Tue, Dec 1, 2015 at 9:04 PM, Stewart, David C wrote: > On 12/1/15, 10:56 AM, "Maciej Fijalkowski" wrote: > > > >>Hi David. >> >>Any reason you run a tiny tiny subset of benchmarks? > > We could always run more. There are so many in the full set in

Re: [Python-Dev] Avoiding CPython performance regressions

Hi Thanks for doing the work! I'm on of the pypy devs and I'm very interested in seeing this getting somewhere. I must say I struggle to read the graph - is red good or is red bad for example? I'm keen to help you getting anything you want to run it repeatedly. PS. The intel stuff runs one

Re: [Python-Dev] Avoiding CPython performance regressions

On Mon, Nov 30, 2015 at 3:33 PM, Stewart, David C wrote: > > On 11/30/15, 5:52 AM, "Python-Dev on behalf of R. David Murray" > rdmur...@bitdance.com> wrote: > > > > >There's also an Intel project

Re: [Python-Dev] Avoiding CPython performance regressions

On Tue, Dec 1, 2015 at 6:36 AM, Maciej Fijalkowski wrote: > Hi > > Thanks for doing the work! I'm on of the pypy devs and I'm very > interested in seeing this getting somewhere. I must say I struggle to > read the graph - is red good or is red bad for example? > > I'm keen to

Re: [Python-Dev] Avoiding CPython performance regressions

On Tue, Dec 1, 2015 at 11:49 AM, Fabio Zadrozny wrote: > > On Tue, Dec 1, 2015 at 6:36 AM, Maciej Fijalkowski wrote: >> >> Hi >> >> Thanks for doing the work! I'm on of the pypy devs and I'm very >> interested in seeing this getting somewhere. I must say I

Re: [Python-Dev] Avoiding CPython performance regressions

@bitdance.com>>, "python-dev@python.org<mailto:python-dev@python.org>" <python-dev@python.org<mailto:python-dev@python.org>> Subject: Re: [Python-Dev] Avoiding CPython performance regressions On Mon, Nov 30, 2015 at 3:33 PM, Stewart, David C <david.c.stew...@intel

Re: [Python-Dev] Avoiding CPython performance regressions

On Tue, Dec 1, 2015 at 8:14 AM, Maciej Fijalkowski wrote: > On Tue, Dec 1, 2015 at 11:49 AM, Fabio Zadrozny wrote: > > > > On Tue, Dec 1, 2015 at 6:36 AM, Maciej Fijalkowski > wrote: > >> > >> Hi > >> > >> Thanks for doing the work! I'm on

Re: [Python-Dev] Avoiding CPython performance regressions

On 12/1/15, 7:26 AM, "Python-Dev on behalf of Stewart, David C" wrote: > >Fabio – my advice to you is to check out the daily emails sent to >python-checkins. An example is

Re: [Python-Dev] Avoiding CPython performance regressions

On Tue, Dec 1, 2015 at 9:35 AM, Victor Stinner wrote: > 2015-12-01 10:49 GMT+01:00 Fabio Zadrozny : > > As for the graph, it should be easy to customize (and I'm open to > > suggestions). In the case, as it is, red is slower and blue is faster > (so,

Re: [Python-Dev] Avoiding CPython performance regressions

2015-12-01 10:49 GMT+01:00 Fabio Zadrozny : > As for the graph, it should be easy to customize (and I'm open to > suggestions). In the case, as it is, red is slower and blue is faster (so, > for instance in > https://www.speedtin.com/reports/1_CPython27x_Performance_Over_Time

Re: [Python-Dev] Avoiding CPython performance regressions

On 11/30/15, 5:52 AM, "Python-Dev on behalf of R. David Murray" wrote: > >There's also an Intel project posted about here recently that checks >individual benchmarks for performance regressions and

[Python-Dev] Avoiding CPython performance regressions

Hi python-dev, I've seen that on and off CPython had attempts to measure benchmarks over time to avoid performance regressions (i.e.: https://speed.python.org), but had nothing concrete so far, so, I ended up creating a hosted service for that (https://www.speedtin.com) and I'd like to help in

Re: [Python-Dev] Avoiding CPython performance regressions

On Mon, 30 Nov 2015 09:02:12 -0200, Fabio Zadrozny wrote: > Note that uploading the data to SpeedTin should be pretty straightforward > (by using https://github.com/fabioz/pyspeedtin, so, the main issue would be > setting up o machine to run the benchmarks). Thanks, but Zach