From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: OpenSSL “DROWN” vulnerability & grafts
Date: Sat, 05 Mar 2016 22:51:00 +0100 [thread overview]
Message-ID: <871t7o386z.fsf@gnu.org> (raw)
In-Reply-To: <20160305190735.GA22021@debian-netbook> (Efraim Flashner's message of "Sat, 5 Mar 2016 21:07:35 +0200")
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Sat, Mar 05, 2016 at 12:24:59AM +0100, Ludovic Courtès wrote:
>> Efraim Flashner <efraim@flashner.co.il> skribis:
>>
>> > efraim@debian-netbook:~/workspace/guix$ time ./pre-inst-env guix package -u && time ./pre-inst-env guix package -u && time ./pre-inst-env guix package -u
>> >
>> > real 15m0.833s
>> > user 5m53.268s
>> > sys 1m26.056s
>> >
>> > real 14m27.095s
>> > user 5m50.848s
>> > sys 1m25.156s
>> >
>> > real 14m37.017s
>> > user 5m55.564s
>> > sys 1m30.536s
>> >
>> > so I don't think the substitute info is the part that's slowing it down.
>> > Conky shows me both guix hand guix-daemon working, so more likely something
>> > else, like figuring out the substitutions.
>>
>> Terrible. Commit d4da602 should improve the situation. You’re welcome
>> to try again and report back!
>>
>
> Much better!
Good, thanks for benchmarking!
There are other things (‘bag-grafts’, namely) that are done repeatedly
when doing an upgrade and that would benefit from a bit of
caching/memoization. Coming next!
Ludo’.
prev parent reply other threads:[~2016-03-05 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 21:16 OpenSSL “DROWN” vulnerability & grafts Ludovic Courtès
2016-03-01 21:50 ` Christopher Allan Webber
2016-03-02 16:28 ` Ludovic Courtès
2016-03-02 17:47 ` Mathieu Lirzin
2016-03-02 18:00 ` Chris Marusich
2016-03-02 18:43 ` Efraim Flashner
2016-03-02 21:36 ` Ludovic Courtès
2016-03-03 6:45 ` Efraim Flashner
2016-03-04 23:24 ` Ludovic Courtès
2016-03-05 19:07 ` Efraim Flashner
2016-03-05 21:51 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871t7o386z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/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.