perf.haskell.org functional again
m at tweag.io
Tue Oct 24 07:57:21 UTC 2017
what kind of machine is this running on at the moment? A dedicated
instance or some colocated VM in the cloud? I ask because for perf
results something CircleCI might *not* be suitable here because
execution time on CircleCI varies quite substantially depending on
load from other users of the same physical machine. This is not a
problem for most types of jobs, but perf measurement is one of the few
for which it is, depending on which metrics are tracked.
Of course, we could always have TravisCI/CircleCI drive a dedicated
machine, but it's not clear to me that these services would be the
best fit for this particular use case.
Founder at http://tweag.io.
On 24 October 2017 at 05:46, Joachim Breitner <mail at joachim-breitner.de> wrote:
> Is CircleCI the future now?
> In general, yes. But it’s running fine for now, so I would not
> prematurely throw it over.
> My requirements are:
> * needs to run on every commit (not just every push), including
> * needs to be able to push to a repository¹, so it needs access to
> some secret token for depolyment.
> Alternatively, the CI could simply keep track of the build log
> and the perf.haskell.org dashboard scrapes it from there.
> * Occasionally, I find that I want to rebuild a fair number of commits
> that are already in the repository. So a good way to trigger
> rebuilds would be nice.
> ¹ https://github.com/nomeata/ghc-speed-logs/commits/master
> Am Dienstag, den 24.10.2017, 12:18 +1100 schrieb Manuel M T
>> Hi Joachim,
>> Great! Just because you mention CI infrastructure and our effort around GHC CI at the moment, do you think, it would make sense to move this to CircleCI eventually?
>> > Am 24.10.2017 um 11:02 schrieb Joachim Breitner <mail at joachim-breitner.de>:
>> > Hi,
>> > after a system upgrade to avoid weird linker errors, and after some fixes in the nofib submodule, http://perf.haskell.org/ghc is running again.
>> > I am collecting instruction counts instead of runtime, because the latter was just too often varying too wildly. I hope this will yield less false alarms.
>> > I am also running nofib with mode=fast. This way, building GHC, running the testsuite and nofib takes a bit over one hour. I hope this can keep up with y'all's commits (when it took 2h it couldn't).
>> > Now nothing of the setup requires a quiet dedicated machine, so if there is a need, we could move these builds into the cloud or into some CI infrastructure - but no changes are immediately planned.
>> > Enjoy, Joachim
> Joachim Breitner
> mail at joachim-breitner.de
> ghc-devs mailing list
> ghc-devs at haskell.org
More information about the ghc-devs