public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2024-01-14 - Call for agenda items
Date: Sat, 13 Jan 2024 14:00:08 +0100	[thread overview]
Message-ID: <5440388.aeNJFYEL58@noumea> (raw)
In-Reply-To: <ZZOAEPo4Tl8Z1ilL@gentoo.org>

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

> > Agenda items from Infra:
> > 
> > --------------------------
> > 
> > # Refresh Hetzner servers
> > dilfridge pointed out that demeter.amd64.dev.gentoo.org is being used to
> > build the new binary packages, and is almost at capacity. It's Hetzner's
> > AX51-NVME model, with 64GB RAM & 2x1TB NVME, presently costing ~EUR58/mo
[...]
> > I'd like to move demeter.amd64.dev.gentoo.org's workload to a
> > higher-spec server (new CPU generation, double core count, double RAM,
> > double storage):
> > 
> > Hetzner AX102 or equivalent specification from Hetzner's Server Auction
> > models, cost of EUR104/mo plus EUR39 setup.

An example for the load of demeter is plotted her:
https://dev.gentoo.org/~dilfridge/load-demeter.pdf

Demeter is not only doing the binary packages, but also stages and isos for 
(natively) amd64, x86 and (via qemu) alpha, m68k, loong, riscv, aarch64_be.
Setting to keep it maximally busy are
MAKEOPTS="-j17 -l32"
EMERGE_DEFAULT_OPTS="--jobs 5 --load 32"

I checked the server auction a few days ago and didnt really see anything
obviously better than the AX102 (of course this may have changed in the
meantime).

https://www.hetzner.com/dedicated-rootserver/matrix-ax

A few remarks about the AX102 config:
* the main requirement for the machine is many cores and threads (now 8 cores, 
  AX102 16 cores)
* nvme storage: 2T (now) is OK, 3.8T (AX102) is better
  (mostly to have convenience buffer for bug fixing in qemu nspawns)
* no redundancy required, we can go a few days without package/stage updates,
  a reinstall is easy and the data is kept on other infra machines / 
  mastermirror too anyway
* AX102 is Zen4, which is nice since future-proof (x86-84-v4 anyone?), right 
  now we have Zen2


> > ## Net financial impact:
> > - Demeter new AX102: +104 EUR/mo, +EUR39 setup.
> > - oystercatcher->demeter content swap: 0 EUR/mo change
> > - decom old oystercatcher hardware: -EUR100/mo
> > = Net: EUR4/mo, EUR39 one-time charge.
> > 
> > --------------------------


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-01-13 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 18:14 [gentoo-project] Council meeting 2024-01-14 - Call for agenda items Ulrich Mueller
2024-01-02  1:02 ` Robin H. Johnson
2024-01-02  3:16   ` John Helmert III
2024-01-02 22:37     ` Robin H. Johnson
2024-01-03  6:24       ` Michał Górny
2024-01-03  8:33         ` Robin H. Johnson
2024-01-03 12:01         ` Rich Freeman
2024-01-13 13:00     ` Andreas K. Huettel [this message]
2024-01-08 21:02 ` [gentoo-project] Council meeting 2024-01-14 - agenda Ulrich Mueller

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5440388.aeNJFYEL58@noumea \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox