From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: guix-devel@gnu.org
Subject: Re: Medium-term road map
Date: Mon, 27 Apr 2020 09:06:45 -0400 [thread overview]
Message-ID: <87wo61axi2.fsf@dustycloud.org> (raw)
In-Reply-To: <87pnbtwdh8.fsf@igalia.com>
Andy Wingo writes:
> On Sat 25 Apr 2020 15:37, Ludovic Courtès <ludo@gnu.org> writes:
>
>> 2. Performance. There are many things we can improve there, first and
>> foremost: the “Computing derivation” part of ‘guix pull’, Guile’s
>> compiler terrible time and space requirements
>
> I think I have a solution here, as discussed on IRC. Basic idea is to
> make a direct compiler from Tree-IL to bytecode, skipping the CPS step.
> The result won't be optimal in terms of generated code quality (I
> estimate on average 2x slowdown) but it will be very cheap to produce (I
> estimate 10x improvement in time, and going from O(n log n) space to
> O(n), with better constant factors. We'd use this compiler for -O0 or
> maybe even -O1 code.
>
> Got to spend a few days working it up tho!
>
> Andy
That sound like a nice path to an improvement!
next prev parent reply other threads:[~2020-04-27 13:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 13:37 Medium-term road map Ludovic Courtès
2020-04-25 16:23 ` Pierre Neidhardt
2020-05-03 20:13 ` Ludovic Courtès
2020-04-25 21:38 ` Jack Hill
2020-04-26 1:22 ` Josh Marshall
2020-05-03 20:18 ` Ludovic Courtès
2020-05-06 17:03 ` [EXT] " Thompson, David
2020-05-06 18:58 ` Efraim Flashner
2020-05-06 19:46 ` Jack Hill
2020-05-07 12:24 ` [EXT] " Thompson, David
2020-04-26 16:06 ` zimoun
2020-04-26 18:20 ` Christopher Baines
2020-05-03 20:07 ` Ludovic Courtès
2020-05-04 10:32 ` zimoun
2020-04-26 18:14 ` Christopher Baines
2020-05-03 20:11 ` Ludovic Courtès
2020-04-27 8:16 ` Andy Wingo
2020-04-27 13:06 ` Christopher Lemmer Webber [this message]
2020-04-30 21:27 ` Joshua Branson
2020-05-05 23:50 ` raingloom
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=87wo61axi2.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guix-devel@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.
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.