From: Andreas Enge <andreas@enge.fr>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 32548@debbugs.gnu.org
Subject: bug#32548: Cuirass: Performance monitoring
Date: Wed, 16 Sep 2020 17:56:39 +0200 [thread overview]
Message-ID: <20200916155639.GA16338@jurong> (raw)
In-Reply-To: <87tuw05vom.fsf@gnu.org>
On Mon, Sep 14, 2020 at 03:34:17PM +0200, Mathieu Othacehe wrote:
> I just pushed support for computing and displaying metrics in Cuirass. I
> started with two metrics:
> * Builds per day
> * Average evaluation speed per specification.
> Those metrics can now be seen at:
> https://ci.guix.gnu.org/metrics
Congratulations, that looks like a very useful start already!
(And the number of builds has doubled since yesterday, so someone already
put it to good use!)
How about also adding metrics per build machine? I have the impression,
for instance, that the aarch64 machine in my living room is not used.
If this is confirmed, we could take appropriate action (uncomment it in
/etc/machines.scm :-), compare to other used machines, change the scheduling
in the daemon, or even turn it off to conserve energy should it turn out
that we have too much build power...).
Andreas
next prev parent reply other threads:[~2020-09-16 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 22:33 bug#32548: Cuirass: Performance monitoring Ludovic Courtès
2020-09-06 14:42 ` Mathieu Othacehe
2020-09-06 18:51 ` Christopher Baines
2020-09-07 8:11 ` Ludovic Courtès
2020-09-10 13:26 ` Mathieu Othacehe
2020-09-14 13:34 ` Mathieu Othacehe
2020-09-14 14:10 ` zimoun
2020-09-16 2:21 ` Bonface M. K.
2020-09-14 19:27 ` Ludovic Courtès
2020-09-17 10:07 ` Mathieu Othacehe
2020-09-17 20:22 ` Ludovic Courtès
2020-09-16 15:56 ` Andreas Enge [this message]
2020-09-17 7:10 ` Mathieu Othacehe
2020-09-18 12:21 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200916155639.GA16338@jurong \
--to=andreas@enge.fr \
--cc=32548@debbugs.gnu.org \
--cc=othacehe@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).