unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: hydra: Update the file with the machines in the bayfront build farm.
Date: Sun, 20 Sep 2020 15:22:25 +0200	[thread overview]
Message-ID: <87r1qwoa5q.fsf@gnu.org> (raw)
In-Reply-To: <20200919163305.B1886208D9@vcs0.savannah.gnu.org> (Andreas Enge's message of "Sat, 19 Sep 2020 12:33:05 -0400 (EDT)")

Hi!

andreas@enge.fr (Andreas Enge) skribis:

> --- a/hydra/machines-bayfront.scm
> +++ b/hydra/machines-bayfront.scm
> @@ -5,7 +5,7 @@
>      (user "bayfront")
>      (host-key "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBfd3VZqyoKoZG3X772eDBrN2MPhnNDDnVA34hpf0f9b root@(none)")
>      (parallel-builds 3)
> -    (speed 1.0)))
> +    (speed 8.0)))
>      
>  (define milano
>    (build-machine
> @@ -14,17 +14,17 @@
>      (user "bayfront")
>      (host-key "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPJFpBJSaOK2aDaR48Fm8udhLK9fl5YwNlq43uaLBeRv root@(none)")
>      (parallel-builds 3)
> -    (speed 1.0)))
> +    (speed 32.0)))

‘speed’ should be used with care: in general, you always want it to be
the same (not to be confused with ‘parallel-builds’).  In the case
above, the risk is that milano will always be chosen.

When milano’s load is too high, it’ll fall back to the next machine, but
then it means scheduling is wasting time always contacting machines in
the same order, which goes against the strategy of
‘choose-build-machine’ in (guix scripts offload).

Maybe acceptable when there are few machines, but otherwise not great.
:-)

Ludo’.


       reply	other threads:[~2020-09-20 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200919163302.7428.36764@vcs0.savannah.gnu.org>
     [not found] ` <20200919163305.B1886208D9@vcs0.savannah.gnu.org>
2020-09-20 13:22   ` Ludovic Courtès [this message]
2020-10-04  8:00     ` 03/03: hydra: Update the file with the machines in the bayfront build farm Andreas Enge

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=87r1qwoa5q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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).