unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: guix-devel@gnu.org
Subject: Re: Resource usage excessive after 'guix pull'
Date: Sun, 21 May 2023 19:50:40 +0100	[thread overview]
Message-ID: <87o7mdfrfk.fsf@cbaines.net> (raw)
In-Reply-To: <CAFHYt54k1GV5y_9iAYg0Bz-NsaXsrdLEN9wNLfr617qF0gUwRQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]


Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> writes:

> Today, a 'guix pull' caused an excessive allocation of system
> resources locally. I had rebased and published an experimental branch,
> which only added a targeted (and tested) fix for 'eudev' [1] on top of
> the mainline commit e499cb2c12d7f1c6d2f004364c9cc7bdb7e38cd5. Then I
> issued:
>
>   guix pull --disable-authentication --allow-downgrades
>
> That command ran very slowly and then resulted in the following
> process taking up over 91% memory before being terminated manually via
> 'kill -TERM'. The bare metal equipment has 28 GB of RAM.
>
>   guixbuilder01 3189 39.0 91.4  09:01 03:57
> /gnu/store/ad8351jvj61da279a3ddfs2gmk3whvdq-guile-wrapper/bin/guile
> --no-auto-compile
> /gnu/store/py8f9r0k22hmhahyz7hm7hrbdrvfa9n2-profile/bin/guix repl -t
> machine
>
> Any pointers would be welcome. Thanks!

It's probably not a problem with your changes, the commit from the Guix
master branch that you based your changes on was in a bad state. That's
been fixed now so try rebasing your changes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

      reply	other threads:[~2023-05-21 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21 16:41 Resource usage excessive after 'guix pull' Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-05-21 18:50 ` Christopher Baines [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=87o7mdfrfk.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=felix.lechner@lease-up.com \
    --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 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).