* [bug#48435] Bringing substitutes from the Guix Build Coordinator to users [not found] <878s4ye116.fsf@cbaines.net> @ 2021-05-18 19:45 ` Christopher Baines 2021-05-18 21:24 ` Ludovic Courtès 0 siblings, 1 reply; 2+ messages in thread From: Christopher Baines @ 2021-05-18 19:45 UTC (permalink / raw) To: guix-devel, Ludovic Courtès, Andreas Enge, 48435 [-- Attachment #1: Type: text/plain, Size: 2179 bytes --] Christopher Baines <mail@cbaines.net> writes: > Is there still a path to bring some of these benefits to users, and if > so, what things need doing? It's been a few weeks now, so to summarise, I think only one path emerged, and that is to get substitutes from bayfront to users. Bayfront was already running the Guix Build Coordinator (although only for the last month), and it's now caught up to the point where I'm seeing similar or better substitute availability percentages for x86_64-linux (and powerpc64le-linux) when compared to ci.guix.gnu.org. It's also building i686-linux and aarch64-linux things, but they're still catching up. Obviously just having the substitutes doesn't magically get them to users, so I've started looking in to the changes to start making that happen. Adding the signing key and changing the defaults in a few places seems like a good step forward [1]. 1: https://issues.guix.gnu.org/48435 I want to push on with this within the next couple of weeks, mostly so I can shift focus to Outreachy and the security related tooling work, but also because I still think this will be a good step forward in terms of substitute availability for users. It's been over a year now since implementation started, so it would be good to actually make a positive difference. There's a few issues still on my mind. Even though the substitute availability percentages are good when compared to ci.guix.gnu.org, as bayfront has much less compute power connected, it might not keep up as well when big sets of changes are merged. I think that's just an argument for using the build coordinator on berlin and the connected machines though. The other thing in comparison to ci.guix.gnu.org is that bayfront only has ~4TB of storage rather than ~37TB, and given that currently none of the generated nars are deleted, that will need thinking about in a few months to avoid running out of space. I've had some plans around this for a while [1], but they still require implementing. 1: https://lists.gnu.org/archive/html/guix-devel/2021-02/msg00104.html Apart from merging the changes in [1], I guess a blog post might be useful. Have I missed anything? Chris [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 987 bytes --] ^ permalink raw reply [flat|nested] 2+ messages in thread
* [bug#48435] Bringing substitutes from the Guix Build Coordinator to users 2021-05-18 19:45 ` [bug#48435] Bringing substitutes from the Guix Build Coordinator to users Christopher Baines @ 2021-05-18 21:24 ` Ludovic Courtès 0 siblings, 0 replies; 2+ messages in thread From: Ludovic Courtès @ 2021-05-18 21:24 UTC (permalink / raw) To: Christopher Baines; +Cc: guix-devel, Andreas Enge, 48435 Hello! Christopher Baines <mail@cbaines.net> skribis: > Christopher Baines <mail@cbaines.net> writes: > >> Is there still a path to bring some of these benefits to users, and if >> so, what things need doing? [...] > Obviously just having the substitutes doesn't magically get them to > users, so I've started looking in to the changes to start making that > happen. Adding the signing key and changing the defaults in a few places > seems like a good step forward [1]. > > 1: https://issues.guix.gnu.org/48435 > > I want to push on with this within the next couple of weeks, mostly so I > can shift focus to Outreachy and the security related tooling work, but > also because I still think this will be a good step forward in terms of > substitute availability for users. It's been over a year now since > implementation started, so it would be good to actually make a positive > difference. I’m fine with distributing an extra signing key alongside that of ci.guix.gnu.org. I’m unsure about having two substitute URLs by default since it adds a bit of overhead, though that overhead is only upon cache misses (I have that setup on my laptop actually). It’s also a one-way change: people are likely to keep the defaults “forever”. So we can’t just “experiment” and change our mind later. That means we should at least have a DNS entry that’s not tied to a particular machine, like ci2.guix.gnu.org or whatever. WDYT? Now, what would be nice is to have a second build farm with the K-out-of-N policy you mention in mind. > There's a few issues still on my mind. Even though the substitute > availability percentages are good when compared to ci.guix.gnu.org, as > bayfront has much less compute power connected, it might not keep up as > well when big sets of changes are merged. I think that's just an > argument for using the build coordinator on berlin and the connected > machines though. As much as I’d have preferred a single solution in this area, fueling competition between the Coordinator and Cuirass and their access to official infrastructure doesn’t seem like a viable path to me. I think the primary value in having a second build farm would be reproducibility and doing away with the single point of failure. Overall substitute coverage probably wouldn’t change much. I agree with Mathieu that maintaining it has a cost, but maybe we can try. I realize I’m asking questions rather than providing answers, which may be because I don’t see a clear path ahead. :-) Thanks! Ludo’. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-05-18 21:25 UTC | newest] Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <878s4ye116.fsf@cbaines.net> 2021-05-18 19:45 ` [bug#48435] Bringing substitutes from the Guix Build Coordinator to users Christopher Baines 2021-05-18 21:24 ` Ludovic Courtès
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).