bug#27284: Memory leak in 'guix pull' or 'make' in guix source

[Maxim Cournoyer]

address@hidden (Ludovic Courtès) writes:

> address@hidden (Taylan Ulrich "Bayırlı/Kammer") skribis:
>
>> address@hidden (Ludovic Courtès) writes:
>>
>>> [...]
>>>
>>> There’s also the option of not compiling (gnu packages *) and instead
>>> evaluating them, but currently this is too costly in terms of memory
>>> and CPU.
>>>
>>> [...]
>>
>> Can't we leave this to auto-compilation during normal use of guix?
>
> We’d have the same problem, only at a different point in time (it might
> even be worse because auto-compilation would use -O2 instead of -O0.)

I've experimented a bit with --no-auto-compile (or lack of) and also
realized that it doesn't bring much to the table. Evaluating (rather
than auto-compiling) the modules is much faster and we need to properly
compile those anyway if we are to properly ship a guix binary
substitute.

Maxim