unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Install `guix pull'ed Guix to target partition on system install
Date: Tue, 22 Dec 2020 00:50:17 +0100	[thread overview]
Message-ID: <86y2hq90sm.fsf@gmail.com> (raw)
In-Reply-To: <87k0tbkkxv.fsf@ambrevar.xyz>

Hi Pierre,

On Mon, 21 Dec 2020 at 20:39, Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> On a related topic, if 2 users "guix pull", is the whole checkout cloned
> twice?

From my understanding yes, as I explained before.

Well, I have never timed when installing in a WM a complete Guix System
with the installer.  So I did with Xfce selected; it downloads some
pieces, and it took me around 40 minutes with my connection at less than
2Mbits/s, from selecting language to the reboot.  Then I boot the
installed VM image, open a terminal with the regular user and hit “guix
pull”.  The clone part is fast, couple of minutes, but then it downloads
a lot of substitutes and computes derivations.  This first “guix pull”
as regular user takes 20 minutes on my machine, mainly downloading
substitutes.

However, from my understanding, it is unavoidable because I used the
v1.2 image installer, therefore somehow, I fetched all the substitutes
from v1.2, then this first “guix pull” as user fetched the substitutes
corresponding to origin/master.  But you did not do that and instead
did:

        - guix pull -C my-channels.scm
        - guix system init ... /mnt 
        - reboot

Did you use Tor or something?  And what does “guix describe” as root
say?

Note that the first “guix pull” for another user (right after) takes
only 6 minutes, mainly cloning the repo.  Basically, on this first “guix
pull” for another user, the cloning+authenticating takes on my machine
~5 minutes.

This part could be improved but it is done only once, take less than 5
minutes with less than 2Mbits/s, so currently I am not convinced that it
is really the bottleneck when pulling the first time from a release
image.  Well, it is for sure an issue with low-bandwith network but Guix
is hard to use with low-material though and cloning is maybe the fastest
part. ;-)


Cheers,
simon


  reply	other threads:[~2020-12-21 23:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20  9:12 Install `guix pull'ed Guix to target partition on system install Pierre Neidhardt
2020-12-21 11:57 ` zimoun
2020-12-21 12:26   ` Pierre Neidhardt
2020-12-21 13:07     ` zimoun
2020-12-21 13:33       ` Pierre Neidhardt
2020-12-21 13:56         ` zimoun
2020-12-21 14:47           ` Pierre Neidhardt
2020-12-21 16:26             ` zimoun
2020-12-21 16:49               ` Pierre Neidhardt
2020-12-21 17:06                 ` zimoun
2020-12-21 17:12                   ` Pierre Neidhardt
2020-12-21 17:53                     ` zimoun
2020-12-21 19:39                       ` Pierre Neidhardt
2020-12-21 23:50                         ` zimoun [this message]
2020-12-22 12:28                           ` Ricardo Wurmus
2020-12-22 13:16                             ` zimoun
2020-12-22  0:29 ` zimoun
2020-12-22  9:44   ` Pierre Neidhardt
2020-12-22 10:46     ` zimoun
2020-12-22 11:51       ` Carlo Zancanaro
2020-12-22 13:06         ` zimoun

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=86y2hq90sm.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@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.
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).