unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Parallel downloads
Date: Sat, 09 Nov 2019 18:40:56 +0100	[thread overview]
Message-ID: <87h83d7xsn.fsf@gnu.org> (raw)
In-Reply-To: <875zjxq978.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 06 Nov 2019 17:08:11 +0100")

Hi Pierre!

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>>> - Can we configure the default value?
>>
>> Yup, just pass ‘--max-jobs=N’ to the daemon.
>
> So I suppose you mean to use the `extra-options` field, e.g.
>
> (guix-service-type config =>
>                    (guix-configuration
>                     (inherit config)
>                     (extra-options '("--max-jobs=4"))))

Yes.

> Ludo, what do you think of Tobias suggestion and have an extra knob to
> specifically configure the number of download jobs?

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.

If it _is_ faster, then we need to investigate why that is the case.
For example, I’m aware that for some reason, nginx gives us low
bandwidth when downloading a nar that’s not already in its cache.  Its
probably an nginx misconfiguration issue but I couldn’t find out.  (This
has been discussed before on one of the mailing lists, I think.)

Does that make sense?  :-)

Thanks,
Ludo’.

  reply	other threads:[~2019-11-09 17:41 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 [this message]
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
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=87h83d7xsn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).