From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38167@debbugs.gnu.org
Subject: bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes
Date: Fri, 27 Dec 2019 19:08:48 +0100 [thread overview]
Message-ID: <875zi1hc9b.fsf@gnu.org> (raw)
In-Reply-To: <20191226204555.1abe4d21@scratchpost.org> (Danny Milosavljevic's message of "Thu, 26 Dec 2019 20:45:55 +0100")
Hi!
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Mon, 11 Nov 2019 21:42:24 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> 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.)
>
> How do I do that?
You could look at the output of “guix processes” and find out which
session child process is consuming memory.
> I've attached the process tree, filtered by "grep guix", of the latest such
> occurence (if this E-Mail still makes it before I have no memory left :P).
AFAICS this excludes the actual build process (which runs “guile”, not
“guix”).
HTH!
Ludo’.
next prev parent reply other threads:[~2019-12-27 18:09 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
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 [this message]
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
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=875zi1hc9b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38167@debbugs.gnu.org \
--cc=dannym@scratchpost.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 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).