Richard
The performance tests seem to be causing more confusion than I'd of
liked. A baseline is established from previous performance test runs.
There is a wiki page that may help:
https://gitlab.haskell.org/ghc/ghc/wikis/building/running-tests/performance-tests.
Let me know if that's not sufficiently helpful.
David E
On 3/10/20 11:05 PM, Richard Eisenberg wrote:
Hi all,
I'm very confused by how to do performance testing.
I have a patch that seems to cause a performance regression. So I built the
patch locally (`validate` flavor, with `make`) and then reproduced the
regression. Good. Then, I make a small change, rebuild, commit, and then test.
But now it seems that the baseline has changed. (This took some time to
discover after seemingly non-deterministic results!)
So: how can I make several different commits, with different experiments, switch between
them at will, all without changing my baseline? I do *not* have the magic "metric
decrease" bit in my commit message. Or, at least, I didn't put it there.
Thanks!
Richard
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
--
David Eichmann, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com
Registered in England & Wales, OC335890
118 Wymering Mansions, Wymering Road, London W9 2NF, England
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
