From: Emmanuel Beffara <manu@beffara.org>
To: help-guix@gnu.org
Subject: Re: guix pull performance
Date: Tue, 28 Nov 2023 22:07:25 +0100 [thread overview]
Message-ID: <20231128220725.GC7864@beffara.org> (raw)
In-Reply-To: <86sf6fzsdo.fsf@gmail.com>
Hello again,
De Simon Tournier le 12/10/2023 à 19:02:
> On Thu, 12 Oct 2023 at 15:51, Emmanuel Beffara <manu@beffara.org> wrote:
>
> > Thanks for the pointer. Now I think I understand the reason for this
> > behaviour: Guix has to compile the whole set of modules, including all package
> > definitions, and it is rather slow at that. So I guess I won't expect
> > significant improvement in the near future, but at least it's not an issue
> > with my particular installation!
>
> If it is not already the case, you might be interested by:
>
> https://guix.gnu.org/manual/devel/en/guix.html#Channels-with-Substitutes
I didn't answer to that at the time, but I do use channels with substitutes as
described in the documentation. I only have the default channel as desribed
there, plus a small custom channel in a local git repository where I put
definitions for custom packages and for third-party packages that I need
(which I intend to propose for integration in Guix itself eventually).
I actually use another channel with less libre kernels and firmwares, but I
disabled it for testing pull times (and it doesn't change things much).
Now, even if I didn't expect a significant improvement, I am still badly
surprised by the behaviour of Guix: one month ago, any `guix pull` took 10
minutes to complete, and these days it takes 40 minutes (the same command, on
the same machine in the same conditions). When running a second `guix pull`
while the channels are unchanged, it takes "only" 6 minutes of computation
before telling me that there is nothing to do.
How is it possible that things are four times slower over just one month ?
Did the package collection increase that much ?
Were there structural changes that caused a loss of efficiency ?
Or might there actually be someting wrong with my setup, and in this case how
could I diagnose it ?
Updating Guix is becoming painful, and if run times continue with their
exponential growth, it will become simply unusable.
--
Emmanuel
next prev parent reply other threads:[~2023-11-28 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 11:03 guix pull performance Emmanuel Beffara
2023-10-12 11:24 ` Ignas Lapėnas
2023-10-12 13:51 ` Emmanuel Beffara
2023-10-12 17:02 ` Simon Tournier
2023-11-28 21:07 ` Emmanuel Beffara [this message]
2023-12-01 17:13 ` 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=20231128220725.GC7864@beffara.org \
--to=manu@beffara.org \
--cc=help-guix@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.
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).