From: raingloom@riseup.net
To: Edouard Klein <edou@rdklein.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix --container is RAM hungry
Date: Mon, 25 Mar 2024 09:27:58 +0000 [thread overview]
Message-ID: <9f5fb6729e8a3ab6756e923ce1c6e194@riseup.net> (raw)
In-Reply-To: <87v85fp8bj.fsf@rdklein.fr>
On 2024-03-21 22:44, Edouard Klein wrote:
> Dear Guixers,
>
> I'm a huge fan of guix --container, and I created a system to use those
> by default for network services. But the VPS these services run on has
> only 2GB of RAM, and I just realized that a container, by default,
> requires at least 200MB.
>
> Try it:
> guix shell time which -- bash -c "$(which time) -v guix shell
> --container"
>
> Then Ctrl-D, and look for this line:
> Maximum resident set size (kbytes): 291300
>
> 291MB of RAM to run bash.
>
>
> By contrast, removing the --container option from above yields:
> Maximum resident set size (kbytes): 64496
>
> 64MB, still a lot, but I can live with that.
>
> I tried various calls to unshare, but got no significant increase of
> RAM.
>
> From an outsider's point of view, the --container option is a wrapper
> for unshare, and the dependency resolution is done by guix shell with
> or without the --container option, so I don't understand where the RAM
> explosion come from.
> I mean no implication that '--container' is simple or trivial to
> implement, I just wrestled with namespaces for a few weeks and I know
> they're a pain, to stay polite. I'm thankful for the tool and would like
> to use it more, but I can't in its current state.
>
>
> Any ideas ?
>
> Thanks in advance,
>
> Edouard.
My first guess is that the Guile process is hanging around waiting for
the process it launched, instead of exec-ing into it directly.
next prev parent reply other threads:[~2024-03-25 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 21:44 guix --container is RAM hungry Edouard Klein
2024-03-25 9:27 ` raingloom [this message]
2024-03-26 20:37 ` Ricardo Wurmus
2024-03-28 23:30 ` Ludovic Courtès
2024-03-30 2:33 ` Maxim Cournoyer
2024-04-02 20:33 ` Edouard Klein
2024-04-10 14:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9f5fb6729e8a3ab6756e923ce1c6e194@riseup.net \
--to=raingloom@riseup.net \
--cc=edou@rdklein.fr \
--cc=guix-devel@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 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.