From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Parallel downloads
Date: Sun, 17 Nov 2019 18:15:24 +0100 [thread overview]
Message-ID: <87zhgumnkj.fsf@gnu.org> (raw)
In-Reply-To: <20191112174442.GA25397@jasmine.lan> (Leo Famulari's message of "Tue, 12 Nov 2019 12:44:42 -0500")
Hi,
Leo Famulari <leo@famulari.name> skribis:
> On Sat, Nov 09, 2019 at 06:40:56PM +0100, Ludovic Courtès wrote:
>> Like I wrote, it’s not that simple (we’d first need the daemon to
>> distinguish substitution jobs from other jobs, but note that there are
>> also “downloads” that are actually derivation builds), and it’s not
>> clear to me that it’s overall beneficial anyway: it’s not supposed to be
>> faster to download 10 things in parallel from ci.guix.gnu.org, than to
>> download them sequentially.
>
> Parallel downloading is not faster in terms of overall transfer rate
> from ci.guix.gnu.org.
>
> However, installing things with Guix involves downloading a lot of very
> small files like derivations, and Guix spends a lot of time initiating
> these downloads.
Good point.
Note that .drv files are never downloaded, but nevertheless it’s true
that there are often small files like the “module-import-compiled”
things. This happens when building a system, but not so much when
building a package, though.
> For example, I can download things at 100 megabits, but when Guix needs
> to sequentially download 50 10-kilobyte files, it may take an entire
> minute.
>
> So there is a huge speedup with parallel downloading.
One thing I’d like to get rid of is the initial HTTP GET for
/nix-cache-info which is completely useless now. That could help a bit.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-11-17 17:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 15:07 Parallel downloads Pierre Neidhardt
2019-10-31 16:18 ` Tobias Geerinckx-Rice
2019-10-31 16:48 ` Pierre Neidhardt
2019-10-31 18:01 ` zimoun
2019-10-31 18:09 ` Pierre Neidhardt
2019-11-03 14:48 ` Ludovic Courtès
2019-11-03 15:29 ` Pierre Neidhardt
2019-11-06 15:34 ` Ludovic Courtès
2019-11-06 16:08 ` Pierre Neidhardt
2019-11-09 17:40 ` Ludovic Courtès
2019-11-10 13:28 ` Pierre Neidhardt
2019-11-12 15:36 ` Ludovic Courtès
2019-11-12 15:59 ` John Soo
2019-11-12 16:48 ` zimoun
2019-11-13 7:43 ` Efraim Flashner
2019-11-13 11:26 ` zimoun
2019-11-12 17:44 ` Leo Famulari
2019-11-17 17:15 ` Ludovic Courtès [this message]
2019-11-13 16:16 ` Mark H Weaver
2019-11-13 18:03 ` Pierre Neidhardt
2019-11-13 18:25 ` Leo Famulari
2019-11-13 19:34 ` Pierre Neidhardt
2019-12-13 9:35 ` Pierre Neidhardt
2019-12-13 12:25 ` Brett Gilio
2019-11-17 17:52 ` Ludovic Courtès
2019-11-06 21:26 ` Bengt Richter
2019-11-01 10:06 ` Joshua Branson
2019-11-01 19:11 ` Pierre Neidhardt
2019-11-03 14:50 ` Ludovic Courtès
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=87zhgumnkj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).