From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43564@debbugs.gnu.org
Subject: bug#43564: cuirass: Contention while registering new builds.
Date: Mon, 05 Oct 2020 15:09:06 +0200 [thread overview]
Message-ID: <87k0w47rbh.fsf@gnu.org> (raw)
In-Reply-To: <87v9fo27vz.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 05 Oct 2020 14:07:44 +0200")
Hey Ludo,
> Isn’t that the real problem, that we’re doing one transaction per
> derivation?
Is it really better in term of performance to send batch of queries
within a single transaction? I haven't tried it yet.
I think that the real bottleneck was having N fibers fighting over 4
workers to execute large number of insertions. Having all those queries
done by workers dedicated to registration in a single pass seems to
improve a lot the situation.
Maybe having those registration workers posting unique transactions
containing all the queries would be even more beneficial.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-10-05 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 16:52 bug#43564: cuirass: Contention while registering new builds Mathieu Othacehe
2020-09-28 7:51 ` Mathieu Othacehe
2020-09-28 8:17 ` Mathieu Othacehe
2020-09-29 15:02 ` Mathieu Othacehe
2020-10-04 11:12 ` Mathieu Othacehe
2020-10-05 12:07 ` Ludovic Courtès
2020-10-05 13:09 ` Mathieu Othacehe [this message]
2020-10-09 7:59 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0w47rbh.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=43564@debbugs.gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).