Re: [Speed] Benchmark tooling broken by the migration to Git
Hi Victor,
Codespeed supports both git and Github. When you configure a project in the admin, you should see a dropdown for the type of revision control. Github is probably best so there is no need for locally cloning the git repository.
Anything else that might be a blocker?
Miquel
On Mon, Feb 20, 2017 at 1:58 PM Victor Stinner <victor.stinner@gmail.com> wrote:
Hi,
The website speed.python.org is made of different tools which were written for Mercurial, but CPython moved to Git. These tools should be updated.
Tools:
- The Django application "codespeed"
- scripts/bench_cpython.py and scripts/bench_revisions.py of https://github.com/python/performance/
- my private tool to benchmark a patch -- short bash script, sorry I should put it in python/performance/scripts/ as well
- maybe others
Moreover, all benchmark results was generated using Mercurial commit identifiers. We must remove all of them and recompute all results using Git commit identifiers. It's not a big deal. It's just that someone has to do it.
I spent almost a year to fix all these minor things to get a working speed.python.org, so I'm not ready to do it right now. I may do the required changes later ;-)
If codespeed doesn't support Git, I suggest to drop the list of changes between two commits on the https://speed.python.org/changes/ tab. I'm now trying to only compute benchmarks manually something like once per week, because the UI doesn't handle well too many points, and because performance don't change every day ;-) The changes/ tab is very slow when there is a long list of commits, whereas it's very easy to get this list using Git directly, GitHub, or whatever. I don't think that it's very useful on the website.
Victor
Speed mailing list Speed@python.org https://mail.python.org/mailman/listinfo/speed
participants (1)
-
Miquel Torres