Mercurial performance tracking tool
Philippe Pepiot
philippe.pepiot at logilab.fr
Thu Sep 1 09:16:29 UTC 2016
Hi,
Some news about the state of
https://www.mercurial-scm.org/wiki/PerformanceTrackingSuitePlan on which
I haven't worked during the summer but I'd like to deliver something
useful soon.
We have an online demo running at: https://jenkins.philpep.org/hgperf/
It has detected a regression between 1% and 10% on almost all revset
benchmarks:
https://jenkins.philpep.org/hgperf/#summarylist?sort=2&dir=desc (related
changeset is https://www.selenic.com/hg/rev/abe4eecc). I don't have the
mercurial knowledge required to understand this regression, so I let you
analyze if something needs to be done or not.
Btw, thanks to Pauli Virtanen, the maintainer of Airspeed Velocity, for
this new "summary" page that is very useful, it shows improvements too.
Now my plans is to:
* Introduce the code in main repository, allowing developers to run
"asv compare" that provide a benchmark(s) summary between two given
revisions.
-> Provide a ASV benchmark suite that can be run against
references repositories (eg. mozilla), a simple list of hg perf commands
is a good start.
-> Write some benchmarks like ".t" test, e.g. scenario based
that create a repository and run hg perf commands, and let asv collect
the results.
* Get the tool and web interface running on mercurial infrastructure
(CC'd Kevin).
Any hints and advices are welcome, especially if you known features of
".t" file format that would be useful to this usage.
Also don't hesitate to subscribe to the feed to be notified about
detected regressions: https://jenkins.philpep.org/hgperf/regressions.xml
Cheers,
--
Philippe Pepiot
https://www.logilab.fr
More information about the Mercurial-devel
mailing list