unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>, Andy Wingo <wingo@igalia.com>
Cc: guix-guix-devel <guix-devel@gnu.org>, Feng Shu <tumashu@163.com>
Subject: Re: compiling guix is too slow?
Date: Sat, 01 Jul 2017 15:33:11 +0200	[thread overview]
Message-ID: <874luwffjc.fsf@gnu.org> (raw)
In-Reply-To: <20170629025648.GB16840@jasmine.lan> (Leo Famulari's message of "Wed, 28 Jun 2017 22:56:48 -0400")

Hi,

Leo Famulari <leo@famulari.name> skribis:

> My understanding is that Guile 2.2 traded slower compilation for faster
> execution of compiled programs. Hopefully the performance of the
> compiler will be improved in later updates to Guile.

Yes, that’s a good summary.

Most of the code we compile is package definitions that don’t benefit
from all the fancy optimizations, so build-aux/build-self.scm (run by
‘guix pull’) turns those off.

Unfortunately even with this change compilation is slower than with
Guile 2.0, and IMO unacceptably slow for ‘guix pull’ (it takes only a
few minutes at most on my laptop, but that’s a lot if we compare to
‘apt-get update’.)

Andy, do you have other approaches in mind that we could explore to
improve on this?  Evaluating all of gnu/packages instead of compiling it
AOT would probably be bad for memory and CPU consumption.

Thanks,
Ludo’.

  reply	other threads:[~2017-07-01 13:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 22:58 compiling guix is too slow? Feng Shu
2017-06-29  1:23 ` Adonay Felipe Nogueira
2017-06-29  2:56 ` Leo Famulari
2017-07-01 13:33   ` Ludovic Courtès [this message]
2017-07-03  7:50     ` Andy Wingo
2017-07-03  8:06       ` ng0
2017-07-03 10:19         ` Ludovic Courtès
2017-07-03 12:15           ` ng0
2017-07-04  9:17             ` Ricardo Wurmus
2017-07-04  9:23               ` ng0
2017-07-03 10:18       ` Ludovic Courtès
2017-06-29  4:28 ` Alex Vong
2017-07-02 20:38   ` Alex Kost
2017-07-04  8:16     ` Alex Vong
2017-07-05  7:35       ` Alex Kost
2017-07-05 14:39         ` Alex Vong
2017-07-06  3:49 ` Chris Marusich
2018-02-05  7:34   ` Can we speed it up? Prev: " Pjotr Prins
2018-02-05  8:15     ` Konrad Hinsen
2018-02-05  8:55       ` Pjotr Prins
2018-02-05  9:56         ` Konrad Hinsen
2018-02-05 10:12           ` Pjotr Prins
2018-02-05 10:15     ` 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=874luwffjc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=tumashu@163.com \
    --cc=wingo@igalia.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).