GNU bug report logs -
#66997
nar-herder uses 10 GiB of resident memory, 100% CPU on hydra-guix-129
Previous Next
To reply to this bug, email your comments to 66997 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#66997
; Package
guix
.
(Wed, 08 Nov 2023 03:53:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 08 Nov 2023 03:53:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
I was looking at top on the hydra-guix-129 node, which runs nar-herder,
and saw this:
--8<---------------cut here---------------start------------->8---
4772 nar-her+ 20 0 28.9g 11.5g 100.0 6.1 55,55 S .nar-herder-rea
--8<---------------cut here---------------end--------------->8---
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?
--
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#66997
; Package
guix
.
(Wed, 08 Nov 2023 15:40:02 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Maxim Cournoyer <maxim.cournoyer <at> 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.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#66997
; Package
guix
.
(Sun, 11 Feb 2024 16:29:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 66997 <at> debbugs.gnu.org (full text, mbox):
Hi,
Christopher Baines <mail <at> cbaines.net> writes:
> Maxim Cournoyer <maxim.cournoyer <at> 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:
--8<---------------cut here---------------start------------->8---
62775 nar-her+ 20 0 903.7g 93.9g 0.0 49.8 22,44 S `- fibers 0
--8<---------------cut here---------------end--------------->8---
It's gobbled up half of the memory of the machine so far, and will
probably keep growing slowly.
Perhaps the machine should be reconfigured & rebooted, as its generation
appears to be from Nov 23. It's been up for 41 days.
--
Thanks,
Maxim
This bug report was last modified 82 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.