Hi,
> Yes, you’re right of course. But I think in the example above Lars was
> reporting the run time of the ‘guix’ command when the graft itself is
> already built. Just the extra code to compute the graft derivation (not
> actually building them) leads to x2 wall-clock time or so.
yes, Ludo is
Hi!
Maxim Cournoyer skribis:
$ time guix environment --ad-hoc --search-paths r-learnr
guix environment --ad-hoc --search-paths r-learnr 5,90s user 0,09s system
210% cpu 2,844 total
$ time guix environment --ad-hoc --search-paths r-learnr --no-grafts
guix environment
Hello!
Ludovic Courtès writes:
> Maxim Cournoyer skribis:
>
>> Lars-Dominik Braun writes:
>>
>>> Hi Maxim,
>>>
Judging from the above, it seems this issue has been resolved.
>>> grafting is still a performance issue imo. Compare for example:
>>>
>>> $ time guix environment --ad-hoc --sea
Maxim Cournoyer skribis:
> Lars-Dominik Braun writes:
>
>> Hi Maxim,
>>
>>> Judging from the above, it seems this issue has been resolved.
>> grafting is still a performance issue imo. Compare for example:
>>
>> $ time guix environment --ad-hoc --search-paths r-learnr
>> guix environment --ad-h
Hello Lars,
Lars-Dominik Braun writes:
> Hi Maxim,
>
>> Judging from the above, it seems this issue has been resolved.
> grafting is still a performance issue imo. Compare for example:
>
> $ time guix environment --ad-hoc --search-paths r-learnr
> guix environment --ad-hoc --search-paths r-lear
