unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix Day: Notes from the CI session
Date: Tue, 9 Feb 2021 16:45:26 -0500	[thread overview]
Message-ID: <YCMCdlnL38z0Cqf6@jasmine.lan> (raw)
In-Reply-To: <87ft26xzci.fsf@inria.fr>

On Mon, Feb 08, 2021 at 06:07:25PM +0100, Ludovic Courtès wrote:
> ## Open issue: new machines
> 
>   - fast ARM servers available
>   - criteria for hardware?
>     - must run free system (stock Guix System)
>   - hosting?
>     - the MDC (in Berlin) wouldn't host Guix-specific non-x86 servers
>     - could rent space (currently renting space for bayfront.guix in Bordeaux, France), but it's relatively costly
>     - workstations could be in people's homes
>       - https://store.avantek.co.uk/ampere-altra-64bit-arm-workstation.html
>         - (benchmark info: https://www.phoronix.com/scan.php?page=article&item=ampere-altra-q80 - compete with AMD Epyc 7nm 2nd Gen)
>       - 
>     - small boards are unreliable or too slow
>     - looking for volunteers to help
>       - pick hardware we could buy
>       - get in touch on `guix-devel` or `guix-sysadmin` (private) mailing lists

I think the status quo of 64-bit ARM for us is untenable. The emulated
builds cause mass failures that can't be reproduced on real hardware.
There is a growing demand for this platform among hobbyists and hackers
who we could convert to Guix contributors!

Regarding hosting, I heard objections to spending significant amounts of
money on it. But, there was also an objection to hosting the machines in
people's homes. Do we know anyone who could donate some rackspace? Or
office-space, if we acquire workstations instead of servers?

As for the hardware itself, yes, it's expensive, but not any more than
what we'd pay for our x86_64 build farm (~1500 CPU cores and terabytes
of RAM). Again, do we know anyone who would donate some? Should we try
negotiating a discount with vendors?

I don't think that using hobbyist SBCs is viable.  It doesn't work for
our armhf platform. Not to mention, the most powerful ones available are
merely dual-core old Cortex-A72 design. For purchasing build farm
hardware, we should look for Cortex-A76, at least, if not Neoverse N1.
Hobbyist SBCs are designed for low-power consumption, not performance;
they are basically re-using SOCs designed for TV boxes and embedded
applications.


  reply	other threads:[~2021-02-09 21:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 17:07 Guix Day: Notes from the CI session Ludovic Courtès
2021-02-09 21:45 ` Leo Famulari [this message]
2021-02-10 17:11   ` Mathieu Othacehe
2021-02-10 17:27     ` Leo Famulari
2021-02-10 21:11     ` Ludovic Courtès
2021-02-13 23:12     ` Leo Famulari
2021-02-14  8:42       ` Mathieu Othacehe
2021-02-14 18:57         ` Leo Famulari
2021-02-10 21:47   ` Ludovic Courtès
2021-02-11 21:04   ` Andreas Enge
2021-02-11 21:16     ` Leo Famulari
2021-02-09 21:46 ` Leo Famulari
2021-02-10 14:09   ` branch naming conventions [was Re: Guix Day: Notes from the CI session] Efraim Flashner
2021-02-10 16:49     ` Leo Famulari
2021-02-10 21:49       ` Ludovic Courtès
2021-02-11 21:14         ` Leo Famulari
2021-02-12  9:57           ` Efraim Flashner

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=YCMCdlnL38z0Cqf6@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).