Untrusem <[email protected]> writes:

> So I came across this article: "How Much Energy Does Building Distro
> Packages Use" [0]
>
> And this made me think "How much energy Guix's infra would be using in
> building packages?", "How can we calculate/monitor it".
>
> I don't think our infra is self-hosted or using solar (maybe in the
> future). So how one would be able generate some data on this?

If you look at https://bordeaux.guix.gnu.org/activity and click "Show
machine details" you'll get some information about the build
machines. There's the location tags, and I've started setting
descriptions which say what the machine is and describing the
hosting. Adding a way of declaring this as part of the bordeaux build
farm configuration would be useful.

Relatively speaking, there's so few machines in the Bordeaux build farm
that it's just not a lot of energy. Given there's machines in France, UK
and Germany, the most carbon intensive machines are probably
hydra-guix-124 and hydra-guix-128 which are hosted by the Max Delbrück
Center in Berlin. ci.guix.gnu.org has more machines though
https://ci.guix.gnu.org/workers

One thing that bothers me more than the energy usage is the waste,
there's plenty of builds that run for a long time and always fail, so
more quickly identifying and fixing/removing these packages would be
good. There's also other efficiency issues like the data service ending
up building stuff for other systems, using expensive emulation and often
the builds fail, but get retried every time a revision is processed
https://codeberg.org/guix/data-service/issues/25

We've also got in to a state recently where changes to packages are
being made inefficiently, just see the recent example of the changes on
the mesa-updates, gnome-team and python-team branches. Each set of
changes affects more than half the packages in Guix, and there's a lot
of overlap since they all affect python. By separating out the changes
this way, the build farms are doing a lot more work, plus users end up
also building/downloading more over and over again. It's a balance, but
I think we need to do better to make changes efficiently as well as at
pace.

Attachment: signature.asc
Description: PGP signature

Reply via email to