RE: perf.haskell.org’s list of branches got more useful
Simon Peyton Jones
simonpj at microsoft.com
Mon Apr 25 09:32:17 UTC 2016
But your email will soon disappear into the mists of time, and the page itself does not convey the same information.
Is there a wiki page, kept up to date, that explains exactly how to read the performance results?
| -----Original Message-----
| From: ghc-devs [mailto:ghc-devs-bounces at haskell.org] On Behalf Of
| Joachim Breitner
| Sent: 23 April 2016 20:41
| To: ghc-devs at haskell.org
| Subject: perf.haskell.org’s list of branches got more useful
| the list of branches
| on https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fper
| sdata=Rk2Y38BjXeE9Et8yxiuOdpiJ3PSMn9RdIxonRksxTc4%3d got more useful.
| It now shows the difference from the branch head to the merge base¹,
| which should roughly exhibit the performance change that would be
| caused by merging the branch into master.
| If the branch head or the merge base have not been measured (e.g.
| because the build failed), the display might be a bit confusing. Same
| with branches that often merge or cherry-pick from master. But in the
| common case of a linear, possibly rebased, feature branch, it should
| work fine.
| ¹ Which, I think, is the youngest commit also reachable from master. Or
| something like that. Consult "man git merge-base" if you want a little
| mind teaser.
| Joachim “nomeata” Breitner
| mail at joachim-breitner.de •
| XMPP: nomeata at joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F
| Debian Developer: nomeata at debian.org
More information about the ghc-devs