Joachim Fabulous. 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? Simon | -----Original Message----- | From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of | Joachim Breitner | Sent: 23 April 2016 20:41 | To: ghc-devs@haskell.org | Subject: perf.haskell.org’s list of branches got more useful | | Hi, | | the list of branches | on https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fper | f.haskell.org%2fghc&data=01%7c01%7csimonpj%40064d.mgd.microsoft.com%7ce | c0ca8588956494efa3308d36baf36f5%7c72f988bf86f141af91ab2d7cd011db47%7c1& | 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. | | Greetings, | Joachim | | ¹ 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@joachim-breitner.de • | https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.jo | achim- | breitner.de%2f&data=01%7c01%7csimonpj%40064d.mgd.microsoft.com%7cec0ca8 | 588956494efa3308d36baf36f5%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata | =ya%2bnaZWlbasw8BSIICImvWjh1x%2fb6%2bTsHJuKRGzu2Rg%3d | XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F | Debian Developer: nomeata@debian.org