From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 43340@debbugs.gnu.org
Subject: [bug#43340] [PATCH 0/5] Speed up archive export/import
Date: Sun, 13 Sep 2020 15:07:26 +0200 [thread overview]
Message-ID: <875z8h7rld.fsf@gnu.org> (raw)
In-Reply-To: <87v9gjh3jq.fsf@gnu.org> (Mathieu Othacehe's message of "Sat, 12 Sep 2020 09:12:09 +0200")
Hi!
Mathieu Othacehe <othacehe@gnu.org> skribis:
>>> Specifically, it implements option #4 (spawning ‘guix authenticate’
>>> once for the whole session, instead of spawning it every time a
>>> store item needs to be signed or authenticated), achieving a ~15x
>>> speedup, which is not bad. :-)
>
> Woo, congrats!
To be clear, it’s 15x on the pathological case where we send only small
store items; the difference is obviously less significant if few store
items are exported or if the store items are large. Now, I expect it to
make a noticeable difference on the typical build farm workload.
>> Below is the new Gantt chart for:
>>
>> perf timechart record guix archive --export -r $(guix build coreutils -d) -v3 >/tmp/dump
>>
>> Most of the work happens in ‘guix authenticate’.
>
> I never used the "timechart" sub-command but it sounds really
> nice. Regarding the option you chose, I think it's the more appropriate
> right now. It's very delicate to dedicate time and effort to tweak
> guix-daemon and how we use it, having in mind that we'd like to get rid
> of it.
Yeah.
> However, the potential short term gains can be so huge, that for now
> it's the best thing to do. I should just do like you, and dive into it
> to see what can be done for contention and locking when using
> 'build-paths' RPC via Cuirass.
Yup, makes sense!
> In the meantime, a short review that I hope to complete next week.
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2020-09-13 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 14:40 [bug#43340] [PATCH 0/5] Speed up archive export/import Ludovic Courtès
2020-09-11 14:51 ` [bug#43340] [PATCH 1/5] daemon: Generalize 'HookInstance' to 'Agent' Ludovic Courtès
2020-09-11 14:51 ` [bug#43340] [PATCH 2/5] daemon: Isolate signing and signature verification functions Ludovic Courtès
2020-09-11 14:51 ` [bug#43340] [PATCH 3/5] daemon: Move 'Agent' to libutil Ludovic Courtès
2020-09-12 7:21 ` Mathieu Othacehe
2020-09-11 14:51 ` [bug#43340] [PATCH 4/5] daemon: Spawn 'guix authenticate' once for all Ludovic Courtès
2020-09-12 7:20 ` Mathieu Othacehe
2020-09-11 14:51 ` [bug#43340] [PATCH 5/5] authenticate: Cache the ACL and key pairs Ludovic Courtès
2020-09-11 15:01 ` [bug#43340] [PATCH 0/5] Speed up archive export/import Ludovic Courtès
2020-09-12 7:12 ` Mathieu Othacehe
2020-09-13 13:07 ` Ludovic Courtès [this message]
2020-09-14 13:47 ` bug#43340: " 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=875z8h7rld.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43340@debbugs.gnu.org \
--cc=othacehe@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.