From: Dariqq <dariqq@posteo.net>
To: 74381@debbugs.gnu.org
Subject: bug#74381: High memory usage during guix pull (i686-linux, guile jit)
Date: Thu, 19 Dec 2024 16:54:04 +0000 [thread overview]
Message-ID: <a9f06663-01e4-4b47-8a1e-7330135d5c4c@posteo.net> (raw)
In-Reply-To: <3faad437-c87c-44d0-ad77-9e42418bf2dd@posteo.net>
It turns out disabling guile jit does not work reliably and even without
it guix pull may oom building guix-packages-base using 3GB+ of RAM.
My workaround for now is to run 'guix pull -s i686-linux -p
/tmp/whatever' on an x86_64 machine (to have more RAM available) with
guile jit disabled multiple times until it succeeds (not exactly sure
why that works, is something getting cached somewhere?) and use that
machine to serve substitutes.
After mentioning this on irc today janneke mentioned this commit
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=15c5f1a2c20b21de0f19f42db1ccab4c42117ebb
which reduces the number of files per chunk from 25 to 10 to get guix
pull working on the 32 bit hurd.
I tried reducing that even further to 5 in my local checkout and the max
RAM usage went to (a little bit more reasonable) 1.5-2 GB (both on i686
natively and when emulating with -s i686 with and without guile jit).
This would be still not enough for my little machine but might be enough
for the substitute servers to build it reliably.
I also wanted to try this in a i586-gnu childhurd but guix pull
immediately segfaulted.
prev parent reply other threads:[~2024-12-19 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 12:58 bug#74381: High memory usage during guix pull (i686-linux, guile jit) Dariqq
2024-12-19 16:54 ` Dariqq [this message]
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=a9f06663-01e4-4b47-8a1e-7330135d5c4c@posteo.net \
--to=dariqq@posteo.net \
--cc=74381@debbugs.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 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).