unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 51472@debbugs.gnu.org
Subject: bug#51472: substitute servers should be preferred according to their coverage rate
Date: Thu, 28 Oct 2021 22:07:39 -0400	[thread overview]
Message-ID: <87k0hwa8ic.fsf@gmail.com> (raw)

Hello,

When using substitute servers discovery, I've noticed that if one of the
substitute servers doesn't have any substitutes available, it'll keep
getting tried instead of others, leading to a slide-show of substitutes
updates such as:

--8<---------------cut here---------------start------------->8---
normalized load on machine '127.0.0.1' is 0.04
building /gnu/store/ajd0hx104702jpz2ycdwgrnyrv8jsp6d-xorg-server-21.1.0.tar.xz.drv...
process 9195 acquired build slot '/var/guix/offload/127.0.0.1:6666/1'
normalized load on machine '127.0.0.1' is 0.04
building /gnu/store/49rqi3wpvdm5pv6in9pamzdvg0wscrl8-xorgproto-2021.5.drv...
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://127.0.0.1:8080'... 100.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
substitute: updating substitutes from 'http://127.0.0.1:8080'... 100.0%
substitute: updating substitutes from 'http://192.168.10.102:80'...   0.0%
--8<---------------cut here---------------end--------------->8---

We should implement some scheme to prefer querying high-substitute
servers first, instead of wasting time querying servers always failed
queries; this would greatly improve performance when using substitute
discovery for example combined with low coverage.

Thanks!

Maxim




             reply	other threads:[~2021-10-29  2:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  2:07 Maxim Cournoyer [this message]
2021-11-07 15:11 ` bug#51472: substitute servers should be preferred according to their coverage rate Ludovic Courtès
2022-01-11  3:43   ` Maxim Cournoyer

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=87k0hwa8ic.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=51472@debbugs.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).