unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: help-guix@gnu.org
Subject: Re: How/When will guix pull stop to compile the 616 files?
Date: Tue, 8 Aug 2017 16:39:21 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1708081628270.878@bog.hcoop.net> (raw)
In-Reply-To: <87fud1olks.fsf@elephly.net>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 684 bytes --]

On Tue, 8 Aug 2017, Ricardo Wurmus wrote:

>
> Paul Dufresne <dufresnep@gmail.com> writes:
>
>> It takes 45 mins. on my relatively old dual core to guix-pull
>
> Yeah, this isn’t great.  Since 0.13.0 compilation is slower and requires
> a whole lot more memory.  That’s a known problem.
>
> There are some ideas to reduce the amount of compilation that has to
> happen locally, but it isn’t quite as simple as a first look may
> suggest.

Could building be avoided entirely with substitutes? Are substitutes not 
appropriate for some reason, or is it just that substitutes are not 
produced on Hydra for every guix commit?

Thanks for clearing this up for a Guix beginner.

Jack

  reply	other threads:[~2017-08-08 20:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  0:59 How/When will guix pull stop to compile the 616 files? Paul Dufresne
2017-08-08  1:43 ` Paul Dufresne
2017-08-08  7:50   ` Alex Sassmannshausen
2017-08-08 13:02     ` Paul Dufresne
2017-08-08 20:23       ` Ricardo Wurmus
2017-08-08 20:39         ` Jack Hill [this message]
2017-08-09  5:43           ` Paul Dufresne
2017-08-09  8:08           ` Ricardo Wurmus
2017-08-09 13:41             ` Jack Hill
2017-08-13  3:21       ` Quiliro Ordonez Baca

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=alpine.DEB.2.02.1708081628270.878@bog.hcoop.net \
    --to=jackhill@jackhill.us \
    --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).