From: Julien Lepiller <julien@lepiller.eu>
To: 49439@debbugs.gnu.org, iskarian@mgsn.dev, rekado@elephly.net
Subject: bug#49439: grafts cause “guix environment” to get killed with OOM
Date: Tue, 27 Jul 2021 10:52:44 -0400 [thread overview]
Message-ID: <464151E3-FBF5-4B80-947E-0F1291FD879D@lepiller.eu> (raw)
In-Reply-To: <86tuklr5g6.fsf@mgsn.dev>
[-- Attachment #1: Type: text/plain, Size: 3171 bytes --]
I have a similar issue with an ocaml package I use at work. It's not free software, but all its dependencies are. The dependencies are not all yeet in guix, so to reproduce you might have to import them first with "guix import opam -r foo" for ocaml-foo.
The package depends on ocaml-ounit, ocaml-lp, ocaml-apronext, menhir, ocaml-async, ocaml-core, ocaml-graph, ocaml-libsvm, ocaml-minisat, ocaml-ppx-deriving-yojson, ocaml-yojson, ocaml-z3, ocaml-zarith and z3.
In total, that's 118 transitive inputs. Building the profile takes 30 minutes for me, on an SSD. The builder takes 1.5g resident.
Other than that, I measured time and memory for creating the environment when the profile was already built (no more derivation to build):
`which time` -v ~/guix/pre-inst-env guix environment ocaml-dummy-package -- echo done
User time: 121.43s
System time: 2.28s
Maximum resident: 1803028kB (1.8 GB)
With a warning from GC:
Repeated allocation of very large block (approx. size 35606528)
Note that I get the same numbers with --no-grafts, so it might be a different issue.
"guix build" terminates quickly.
Le 23 juillet 2021 00:59:21 GMT-04:00, Sarah Morgensen <iskarian@mgsn.dev> a écrit :
>Hello,
>
>Ricardo Wurmus <rekado@elephly.net> writes:
>
>> With a recent version of Guix, “guix environment” will not
>> terminate on its own, keeps the CPU busy, and gets killed when the
>> system eventually runs out of memory.
>>
>> $ guix describe -f channels
>>
>> (list (channel
>> (name 'guix)
>> (url "/home/rekado/dev/gx/branches/master")
>> (commit
>> "685cfdec94e5e48c4ad28de53466a28dfc258edb")))
>>
>>
>> $ guix environment pigx-scrnaseq
>> [wait until it gets killed]
>
>I can reproduce this with pigx-scrnaseq as well a number of other
>packages (listed below).
>
>$ ./pre-inst-env guix describe -f channels
>(list (channel
> (name 'guix)
> (url "/home/sarah/guix")
> (commit
> "3217a04b0352c2dd13323257b369604eeabfccc3")))
>
>Does not complete within 5 minutes:
>package # inputs # transitive inputs
> (from package-transitive-inputs)
>pigx-chipseq 48 338
>pigx-scrnaseq 41 321
>r-cellchat 34 110
>pigx-rnaseq 34 343
>pigx-bsseq 32 358
>pigx-sars-cov2-ww 25 261
>r-circus 16 134
>
>Does complete:
>r-chipseq 6 37 completes in >2m
>r-shortread 17 36 completes in >1m
>python-scanpy 25 113 completes in <15s
>
>I suspect it has something to do with the number of transitive inputs,
>because it is so prevalent with these R packages, which all use
>propagated inputs. However... python-scanpy succeeds in under 15
>seconds, and it has more transitive inputs than r-chipseq.
>
>Can we reproduce this with a large number of low-transitivity packages
>directly on the command line?
>
>>
>> The problem disappears when grafts are disabled:
>>
>> $ guix environment --no-grafts pigx-scrnaseq
>> $ [env] yay!
>
>--
>Sarah
[-- Attachment #2: Type: text/html, Size: 3790 bytes --]
next prev parent reply other threads:[~2021-07-27 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 14:38 bug#49439: grafts cause “guix environment” to get killed with OOM Ricardo Wurmus
2021-07-23 4:59 ` Sarah Morgensen
2021-07-27 14:52 ` Julien Lepiller [this message]
2021-07-27 16:28 ` Ludovic Courtès
2021-07-27 23:35 ` Sarah Morgensen
2021-07-28 10:00 ` Ludovic Courtès
2021-07-28 22:03 ` Ludovic Courtès
2021-07-29 3:20 ` Sarah Morgensen
2021-08-09 21:26 ` Ludovic Courtès
2021-08-10 15:36 ` 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=464151E3-FBF5-4B80-947E-0F1291FD879D@lepiller.eu \
--to=julien@lepiller.eu \
--cc=49439@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
--cc=rekado@elephly.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 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.