Zachary Ware told me on IRC that it's ok for him to drop old data.

If nobody else complains, I will remove old data tomorrow (tuesday).

I already validated that the patched scripts work on Git. I released new versions of perf and performance to make sure that the latest version of the code is released and used. By the way, the newly released perf 1.1 gets a new "perf command" command to measure the time of a command, it's like the Unix "time" command.

http://perf.readthedocs.io/en/latest/cli.html#command-cmd

$ python3 -m perf command -- python2 -c pass ..................... command: Mean +- std dev: 21.2 ms +- 3.2 ms

Victor

2017-03-27 0:12 GMT+02:00 Victor Stinner <victor.stinner@gmail.com>:

Hi,

I'm going to remove old previous benchmark results from speed.python.org. As we discussed previously, there is no plan to keep old results when we need to change something. In this case, CPython moved from Mercurial to Git, and I'm too lazy to upgrade the revisions in database. I prefer to run again benchmarks :-)

My plan:

• Remove all previous benchmark results
• Run benchmarks on master, 2.7, 3.6 and 3.5 branches
• Run benchmarks on one revision per year quarter on the last 2 years
• Then see if we should run benchmarks on even older revisions and/or if we need more than one plot per quarter.
• Maybe one point per month at least? The problem is that the UI is limited to 50 points on the "Display all in a grid" view of the Timeline. I would like to be able to render 2 years on this view.

For each year quarter, I will use the first commit of the master branch on this period.

Victor