From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 38167@debbugs.gnu.org
Subject: bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes
Date: Mon, 11 Nov 2019 21:42:24 +0100 [thread overview]
Message-ID: <878somno0f.fsf@gnu.org> (raw)
In-Reply-To: <87eeyec18l.fsf@cbaines.net> (Christopher Baines's message of "Mon, 11 Nov 2019 07:37:30 +0000")
Hi Chris & Danny,
Christopher Baines <mail@cbaines.net> skribis:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> Hi,
>>
>> guix pull takes over 8 GiB of memory to finish if there are no substitutes.
>>
>> My laptop only takes max 8 GiB of RAM. I've set up swap, but that kind of
>> memory usage still seems ridiculous.
>
> Do you know if the derivations got built in parallel? So, does guix pull
> --max-jobs=1 use the same amount of memory?
Also, it would be great if you could identify which derivation build
requires that much memory, if this was happening sequentially. (I
suspect “guix-packages.drv” is the one that eats up the most memory.)
I agree it’s ridiculous. That memory usage comes from Guile’s
compiler. A couple of years ago, Andy managed to cut memory usage
somewhat, but that’s not enough.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-11-11 20:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 7:06 bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes Danny Milosavljevic
2019-11-11 7:37 ` Christopher Baines
2019-11-11 20:42 ` Ludovic Courtès [this message]
2019-12-26 19:45 ` Danny Milosavljevic
2019-12-26 19:48 ` Danny Milosavljevic
2019-12-27 18:11 ` Ludovic Courtès
2019-12-28 11:01 ` Danny Milosavljevic
2019-12-28 14:52 ` Ludovic Courtès
2019-12-28 17:55 ` Danny Milosavljevic
2019-12-29 22:41 ` Ludovic Courtès
2019-12-31 15:44 ` Danny Milosavljevic
2019-12-31 18:18 ` Ludovic Courtès
2020-01-01 12:51 ` Danny Milosavljevic
2020-10-09 2:11 ` Maxim Cournoyer
2019-12-27 18:08 ` Ludovic Courtès
2019-12-28 10:56 ` Danny Milosavljevic
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=878somno0f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38167@debbugs.gnu.org \
--cc=mail@cbaines.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.