From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Speeding up “guix pull”: splitting modules
Date: Wed, 08 Jan 2020 22:57:00 +0100 [thread overview]
Message-ID: <87sgkpd32r.fsf@gnu.org> (raw)
In-Reply-To: <87k1657i7j.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 05 Jan 2020 21:37:36 +0100")
BTW, there’s also the “Compute Guix derivation” phase that could be sped
up, and that’s mostly independent of Guile.
Things that could help include: “recursive Nix”¹ (the Guix derivation
would itself be the result of a derivation, thus subject to
substitutes), or something equivalent without special daemon support
where we’d simply embed (guix derivations) & co. to compute the
derivation in memory.
Another less elegant option would be to resort to a service (Data
Service or Cuirass) that would map a Guix commit to its .drv, and then
fetch that .drv from substitute servers and build it.
Finally, we could/should also profile that phase and see what can be
done.
Lastly :-), it would be great to profile this phase over time to see how
it evolves. (Does the Guix Data Service already stores timings for such
things?)
Ludo’.
¹ https://github.com/NixOS/nix/pull/3205
next prev parent reply other threads:[~2020-01-08 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 20:37 Speeding up “guix pull”: splitting modules Ricardo Wurmus
2020-01-06 9:11 ` Andy Wingo
2020-01-07 18:37 ` zimoun
2020-01-07 20:14 ` Gábor Boskovits
2020-01-10 12:09 ` zimoun
2020-01-10 12:42 ` Gábor Boskovits
2020-01-10 12:53 ` zimoun
2020-01-11 23:29 ` Ludovic Courtès
2020-01-20 17:44 ` zimoun
2020-01-08 21:50 ` Ludovic Courtès
2020-01-10 12:13 ` zimoun
2020-01-10 19:02 ` Ricardo Wurmus
2020-01-08 21:57 ` Ludovic Courtès [this message]
[not found] ` <87zhenp01v.fsf@cbaines.net>
2020-01-19 21:07 ` 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=87sgkpd32r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.