Hi, Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> skribis:
> When updating, my equipment spends nearly as much time "updating > substitutes" as it does downloading substitutes. > > The activity is probably exacerbated because I cross-publish substitutes > in my local network. > > Would it be more efficient to check whether a particular substitute is > available in an individual query (like DNS) and stop querying for that > substitute after a server was found? The “updating substitutes” bit corresponds to making pipelined GET requests for narinfos¹ to figure out upfront what’s going to be available as substitutes and what will have to be built. There’s a cache at /var/guix/substitute/cache so Guix doesn’t send the same request several times in a row. I’m not sure there’s much to be optimized in this area, but perhaps we’d find something by studying more closely pathological cases? Thanks, Ludo’. ¹ Like <https://ci.guix.gnu.org/fk39d3y3zyr6ajyzy8d6ghd0sj524cs5.narinfo>.
