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:50:03 +0100 [thread overview]
Message-ID: <87zhexd3ec.fsf@gnu.org> (raw)
In-Reply-To: <87k1657i7j.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 05 Jan 2020 21:37:36 +0100")
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
> On the other hand: this would need to be an ongoing effort. Newly
> introduced packages or even new features might create complex module
> cycles. It sounds tedious to keep track of this and to enforce
> boundaries.
Yes, I think this is a dead end: glibc could well end up become on
Haskell (hi, Pandoc!), and then the whole module split effort collapses.
Ultimately, I think we need to look into optimizing the compiler. The
profiling I did a while back¹ suggests pessimal behavior of some of the
compiler phases when given large inputs.
Ludo’.
¹ https://lists.gnu.org/archive/html/guile-devel/2017-10/msg00035.html
(I’ve been meaning to resume that investigation for a long time, but
I’d really need to do nothing but that for a couple of weeks…)
next prev parent reply other threads:[~2020-01-08 21:50 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 [this message]
2020-01-10 12:13 ` zimoun
2020-01-10 19:02 ` Ricardo Wurmus
2020-01-08 21:57 ` Ludovic Courtès
[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
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=87zhexd3ec.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 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).