From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 32548@debbugs.gnu.org
Subject: bug#32548: Cuirass: Performance monitoring
Date: Fri, 18 Sep 2020 14:21:37 +0200 [thread overview]
Message-ID: <87mu1nxoku.fsf@gnu.org> (raw)
In-Reply-To: <87een098un.fsf@gnu.org> (Mathieu Othacehe's message of "Thu, 17 Sep 2020 09:10:40 +0200")
Hi Mathieu!
Mathieu Othacehe <othacehe@gnu.org> skribis:
>> 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...).
>
> Yes I would really like to have something like:
> https://hydra.nixos.org/machines, with a build rate for every machine.
+1!
> However, it cannot be done without structural changes to how offloading
> is handled. For now it's working this way:
>
> Cuirass -> guix-daemon -> guix offload -> build machines
>
> Which means that Cuirass has almost no information about offloaded
> builds.
In practice, it could parse the offload events that it gets; a bit of a
hack, but good enough. However…
> We are currently starting discussions about inviting the Guix Build
> Coordinator to the party.
… this sounds like the better option longer-term.
Ludo’.
prev parent reply other threads:[~2020-09-18 12:22 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
2020-09-17 7:10 ` Mathieu Othacehe
2020-09-18 12:21 ` Ludovic Courtès [this message]
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=87mu1nxoku.fsf@gnu.org \
--to=ludo@gnu.org \
--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).