From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39728@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>,
zimoun <zimon.toutoune@gmail.com>
Subject: [bug#39728] [PATCH v2] Allow parallel downloads and builds
Date: Thu, 25 Nov 2021 14:01:45 +0100 [thread overview]
Message-ID: <20211125140145.1c00decc@tachikoma.lepiller.eu> (raw)
In-Reply-To: <87ilwge6re.fsf@gnu.org>
Le Thu, 25 Nov 2021 13:53:25 +0100,
Ludovic Courtès <ludo@gnu.org> a écrit :
> Hello,
>
> Julien Lepiller <julien@lepiller.eu> skribis:
>
> > After so long, I managed to find the time to go over the comments
> > and improve my patches. I tested the new daemon for a bit, and it's
> > working as expected so far :D
>
> On a recent daemon, have you seen cases where having multiple
> downloads in parallel speeds things up?
>
> The analysis in
> <https://guix.gnu.org/en/blog/2021/getting-bytes-to-disk-more-quickly/>
> suggests that at the time you first submitted this patch, substitution
> speed (which is different from raw download speed) was often
> CPU-bound. This is no longer the case, meaning that downloads should
> now be network-bound or almost.
>
> Thanks,
> Ludo’.
I would still say yes, because the output from berlin is often much
less than my throughput. With multiple downloads in parallel it at
least feels quicker, probably because I can download at full speed.
In any case, I see often a build start while downloads are in progress,
so I think it's still a win if you can get a few derivations built
while waiting for a big download to finish at the same time :)
At some point we might want to prioritize builds/downloads that help
unlock as much builds as possible early, so we don't have builds
waiting for downloads.
next prev parent reply other threads:[~2021-11-25 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 22:53 [bug#39728] [PATCH] Allow parallel downloads and builds Julien Lepiller
2020-02-24 21:23 ` Ludovic Courtès
2020-02-25 15:21 ` zimoun
2020-02-25 15:39 ` Julien Lepiller
2020-02-26 10:36 ` Pierre Neidhardt
2021-11-21 22:49 ` [bug#39728] [PATCH v2] " Julien Lepiller
2021-11-25 12:53 ` Ludovic Courtès
2021-11-25 13:01 ` Julien Lepiller [this message]
2021-11-26 10:16 ` Ludovic Courtès
2021-07-14 2:49 ` [bug#39728] [PATCH] " 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=20211125140145.1c00decc@tachikoma.lepiller.eu \
--to=julien@lepiller.eu \
--cc=39728@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=zimon.toutoune@gmail.com \
/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).