Joachim, This looks awesome! Yes, we can set up you up with a small server soon to do all this and keep it running in public.
FWIW, I'd rather not make a virtual proxy at ghc.haskell.org point to your backend server, by routing '/speed' out to another server. What about a new domain - https://speed.ghc.haskell.org ? This falls in line with the new buildbot naming conventions we voted on a few weeks ago, it's trivial to add (only a DNS entry), and is nicer IMO. On Wed, Jan 7, 2015 at 3:54 AM, Simon Peyton Jones <[email protected]> wrote: > Sounds amazing, thank you! > > Simon > > | -----Original Message----- > | From: ghc-devs [mailto:[email protected]] On Behalf Of Joachim > | Breitner > | Sent: 06 January 2015 23:21 > | To: [email protected] > | Subject: New performance dashboard front-end > | > | Hi, > | > | over the holidays I’ve been working on a new and custom-made¹ front-end > | for our performance data, mainly to work around limitations of codespeed > | when it comes to understanding git, but also to add other features that > | I happen to want. > | > | I put a (not automatically updated) preview on > | http://deb.haskell.org/speed/ > | The code is not yet online, and there are some features missing (most > | notably: Working with multiple builders, the per-benchmark-graphs.) > | > | I’d like to have this hosted somewhere properly, so this is a request > | for the infrastructure team. > | > | I am a big fan of static content, so the system is a (shake-driven) > | batch process that generates a bunch of .json file. These can be served > | statically, together with the completely static index.html and a few > | javascript libraries. So it’s all very CDN-friendly. > | > | So all I need is > | * shell access to some machine, preferably with ghc installed > | * some disk space (actually quite a bit due to all the build logs, > | although that could be reduced by gzipping or reading them directly > | from the git repo²) > | * a new virtual host or a subdirectory of http://ghc.haskell.org/ > | where I can deploy my files to. > | * the possibility to either run a cronjob to poll for new logs, or > | maybe (later) some more sophisticated trigger. > | > | Would that be possible? > | > | Greetings, > | Joachim > | > | ¹ It is still a generic display of "values per git commit", and I hope > | I can keep it that way – maybe other projects can use it as well. > | > | ² currently at https://github.com/nomeata/ghc-speed-logs > | If the above becomes official, this probably also should move to > | git.haskell.org. The repo is 250M, but 7,2G checked out. I plan to > | make my code read the logs directly from the repo, and link to the > | cgit web interface to show the logs, so that it never has to be > | checked out. > | > | -- > | Joachim “nomeata” Breitner > | [email protected] • http://www.joachim-breitner.de/ > | Jabber: [email protected] • GPG-Key: 0xF0FBF51F > | Debian Developer: [email protected] > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/ghc-devs -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/ _______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
