unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: 66997-done@debbugs.gnu.org
Subject: bug#66997: nar-herder uses 10 GiB of resident memory, 100% CPU on hydra-guix-129
Date: Sun, 02 Jun 2024 20:22:01 -0400	[thread overview]
Message-ID: <87ttiakh92.fsf@gmail.com> (raw)
In-Reply-To: <87mss7vude.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 11 Feb 2024 11:27:41 -0500")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hi,
>
> Christopher Baines <mail@cbaines.net> writes:
>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>
>>> I was looking at top on the hydra-guix-129 node, which runs nar-herder,
>>> and saw this:
>>>
>>> 4772 nar-her+  20   0   28.9g  11.5g 100.0   6.1     55,55 S .nar-herder-rea
>>>
>>> 11.5 GiB of memory seems a bit excessive, no?  Its cumulated processing
>>> time is also at the top of the table, and it seems stuck at 100% of CPU
>>> usage.
>>>
>>> Is this expected of the nar-herder, or has it gone awry?
>>
>> I think hydra-guix-129 was running an older version of the nar-herder,
>> so I've updated it and I think that's improved the situation.
>>
>> I've just reconfigured the machine to use a specific commit at the
>> moment, but it would be good to bump the commit that the Guix package is
>> using.
>
> The situation appears unresolved; c.f. `top' output on hydra-guix-129:
>
> 62775 nar-her+  20   0  903.7g  93.9g   0.0  49.8     22,44 S  `- fibers 0 

This has since been resolved; it currently uses 675.6 MiB on
hydra-guix-129.

Thanks, Christopher!

-- 
Thanks,
Maxim




      reply	other threads:[~2024-06-03  4:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  3:51 bug#66997: nar-herder uses 10 GiB of resident memory, 100% CPU on hydra-guix-129 Maxim Cournoyer
2023-11-08 15:36 ` Christopher Baines
2024-02-11 16:27   ` Maxim Cournoyer
2024-06-03  0:22     ` Maxim Cournoyer [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=87ttiakh92.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=66997-done@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 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).