From: Josselin Poiret <dev@jpoiret.xyz>
To: Simon Tournier <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: Guix pull speed
Date: Wed, 06 Sep 2023 11:45:15 +0200 [thread overview]
Message-ID: <87edjbvdn8.fsf@jpoiret.xyz> (raw)
In-Reply-To: <86wmx4r082.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]
Hi Simon,
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi Josselin,
>
> On Tue, 29 Aug 2023 at 13:58, Josselin Poiret <dev@jpoiret.xyz> wrote:
>
>> After looking a bit more into guix pull speed, or to be more precise the
>> "Computing Guix derivation..." step, which is not substitutable. I've
>> come to the conclusion that the thing that takes the majority of the
>> time is loading the files that define the packages that the new Guix
>> needs to build itself.
>
> Well, on my machine, the bigger bottleneck seems the procedure name
> ’proxy’ which copies stuff around, IIUC. See [1].
Proxy is on the helper script side, it's just waiting for the actual
build script to do its thing.
>> These files are not compiled yet, and worse,
>> loading just (gnu packages guile) ends up loading 361 other package
>> files. You can generate a package graph in GraphML with `guix graph -t
>> module -b graphml guile`, and use e.g. networkx to analyze it.
>
> Hum, is this ’graphml’ something you have not submitted? Or am I
> missing a point? Last time I played with “guix graph”, I wrote a small
> script for bridging with networkx. See [2].
I've committed it pretty recently, and should work OOTB now.
>> You can compare with a compiled check-out of guix by just running the
>> following in a `guix repl`:
>> --8<---------------cut here---------------start------------->8---
>> (use-modules (guix self) (guix monad-repl))
>> ,run-in-store (guix-derivation (getcwd) "0.0-git" #:pull-version 1)
>> --8<---------------cut here---------------end--------------->8---
>> which takes at most 5 seconds on my laptop.
>
> Yeah, that’s fast. :-)
>
> For comparing, what would be the corresponding derivations that “guix
> pull” is building?
It's building the same! Just that building the derivation takes way
longer because it has first to load a bunch of uncompiled guile files.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-09-06 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 11:58 Guix pull speed Josselin Poiret
2023-09-05 17:36 ` Simon Tournier
2023-09-06 9:45 ` Josselin Poiret [this message]
2023-09-06 19:45 ` Simon Tournier
2023-09-07 8:36 ` Josselin Poiret
2023-09-07 9:37 ` Simon Tournier
2023-09-14 9:58 ` Ludovic Courtès
2023-09-19 11:55 ` Simon Tournier
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=87edjbvdn8.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).