From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Improving CI throughput
Date: Mon, 24 Aug 2020 16:42:19 +0200 [thread overview]
Message-ID: <877dto2jhw.fsf_-_@gnu.org> (raw)
In-Reply-To: <874kpriytq.fsf@gnu.org> (Mathieu Othacehe's message of "Tue, 28 Jul 2020 14:55:13 +0200")
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
> The current situation is that due to Cuirass/offloading issues such as
> [1], our build farm is most of the time idle. Given our computation
> power, we should be able to bake much more substitutes I think.
>
> Maybe we could also take advantage of the build-coordinator Christopher
> is implementing (+ Guix daemon RPC's over HTTP) to make sure that we are
> able to deal with a distributed build farm efficiently.
>
> Now the question I'm asking myself is: could the ARM substitutes
> situation be solved by improving our CI software stack, or do we really
> need more hardware?
Yeah, this is a ridiculous situation. We should do a hackathon to get
better monitoring of useful metrics (machine load,
time-of-push-to-time-to-build-completion, etc.), to clearly identify the
bottlenecks (crashes? inefficient protocol? scheduling issues? Cuirass
or offload or guix-daemon issue?), and to address as many of them as we
can.
Any volunteers? :-)
Ludo’.
next prev parent reply other threads:[~2020-08-24 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 10:31 ARM build machines Jonathan Brielmaier
2020-07-28 12:55 ` Mathieu Othacehe
2020-08-24 14:42 ` Ludovic Courtès [this message]
2020-08-24 14:57 ` Improving CI throughput John Soo
2020-08-25 13:32 ` Mathieu Othacehe
2020-08-25 17:44 ` Ricardo Wurmus
2020-08-28 13:51 ` 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=877dto2jhw.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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).