From: John Soo <jsoo1@asu.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Parallel downloads
Date: Tue, 12 Nov 2019 07:59:44 -0800 [thread overview]
Message-ID: <811C4D1E-A2D9-4661-9F10-C068FBE2CA80@asu.edu> (raw)
In-Reply-To: <87r22dp0mv.fsf@gnu.org>
Hi everyone,
I’ve been watching this from afar and one thing and while I have to agree with this:
> .. I suspect there’s little to
> be gained by having several connections in parallel.
I do have to say that more fine grained concurrency would really help speed up builds without substitutes.
Especially on old hardware, some builds can actually exhaust all resources. That means you can’t really get a speed up by bumping the max jobs.
What would help is doing downloads of sources and substitutes asynchronously while a non-substitute job is taking place. If some network activity could be backgrounded, I think you might find build times decrease a lot.
Thanks!
John
next prev parent reply other threads:[~2019-11-12 15:59 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 [this message]
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
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=811C4D1E-A2D9-4661-9F10-C068FBE2CA80@asu.edu \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.