unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Tobias Geerinckx-Rice" <me@tobias.gr>,
	"Ludovic Courtès" <ludo@gnu.org>,
	guix-devel@gnu.org, guix-europe-sac@gnu.org,
	guix-maintainers@gnu.org
Subject: Re: Shutting down qa.guix?
Date: Mon, 11 Dec 2023 13:30:24 +0000	[thread overview]
Message-ID: <878r60zwr1.fsf@cbaines.net> (raw)
In-Reply-To: <87a5qidouw.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]


Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hi,
>
> Christopher Baines <mail@cbaines.net> writes:
>
>> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>>
>>> Christopher Baines 写道:
>>>> it's not the most cost effective setup
>>>
>>> Has this been explained in more detail before?
>>
>> Probably not, beid is currently a CPX51 Hetzner cloud server costing
>> €65.33 a month. This has been useful as it's enabled scaling the
>> resources dynamically, but it would be possible to reduce the costs and
>> still have sufficient RAM/disk space by using a Hetzner server auction
>> machine for example.
>>
>> It's not all about cost though, given the data service is one of the
>> slow points of QA, if we want QA to get faster at giving feedback, it's
>> probably important to not try and cut costs on this part of the system.
>
> Isn't QA mostly slow because of the lack of x86 build machines?  Does
> the head node needs to be powerful itself?  What kind of resources does
> it likes having the most?  CPU?  RAM?  Storage?

There are two key bottlenecks, processing the revisions in the data
service, then the build coordinator performing the builds.

For the data service, lots of RAM helps as computing and building the
derivations for Guix (similar to pull, time-machine, ...) is quite
expensive in CPU and RAM. Also computing all the derivations for each
revision takes a lot of RAM.

Storage is also an issue as beid currently is working with 340G of total
storage and that's almost full, and this doesn't leave any space for
maintenance. More storage means being able to store data about more
patch series at once.

For the build coordinator, the machine doesn't need to be powerful, it
has quite low requirements. While bayfront's storage isn't particularly
fast, it's more than sufficient in terms of hardware. More build
machines, including x86 ones would speed up the test results for patches
and branches though.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2023-12-11 13:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 13:32 November/December update on qa.guix.gnu.org and related things Christopher Baines
2023-12-09 10:39 ` Discontinuing data.guix.gnu.org? Ludovic Courtès
2023-12-09 11:14   ` Christopher Baines
2024-01-09 18:12     ` Ludovic Courtès
2024-01-09 18:33       ` Julien Lepiller
2024-01-09 19:19         ` Gábor Boskovits
2024-01-10  0:38       ` Maxim Cournoyer
2023-12-09 10:54 ` Shutting down qa.guix? Ludovic Courtès
2023-12-09 12:16   ` Christopher Baines
2023-12-09 13:30     ` Tobias Geerinckx-Rice
2023-12-10 10:54       ` Christopher Baines
2023-12-10 16:05         ` Maxim Cournoyer
2023-12-11 13:30           ` Christopher Baines [this message]
2023-12-10 18:50   ` Simon Tournier
2023-12-13 16:43   ` RFC (was Re: Shutting down qa.guix?) Simon Tournier
2024-01-18 12:39   ` [Guix-europe-sac] Shutting down qa.guix? Andreas Enge
2024-01-20 12:57     ` Christopher Baines
  -- strict thread matches above, loose matches on Subject: below --
2023-12-14 13:38 Jing

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=878r60zwr1.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=guix-europe-sac@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    /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).