From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Mark H Weaver" <mhw@netris.org>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Parallel downloads
Date: Wed, 13 Nov 2019 20:34:45 +0100 [thread overview]
Message-ID: <87pnhvfu3u.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87pnhvda3z.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> For these reasons, I'm inclined to think that parallel downloads is the
> wrong approach. If a single download process is not making efficient
> use of the available bandwidth, I'd be more inclined to look carefully
> at why it's failing to do so. For example, I'm not sure if this is the
> case (and don't have time to look right now), but if the current code
> waits until a NAR has finished downloading before asking for the next
> one, that's an issue that could be fixed by use of HTTP pipelining,
> without multiplying the memory usage.
I think so too.
More generally, the Guix daemon jobs can be categorized in 2: downloads
and builds. These 2 categories demands almost complementary hardware
resources for the local machine.
With that in mind, we could have 2 pipelines: one for the builds and one
for the downloads. This, I think, is general enough that it could be
used by default and improve performance for everyone, regardless of your
Internet bandwidth or CPU power.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-11-13 19:34 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnhvfu3u.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.