From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 48007@debbugs.gnu.org
Subject: bug#48007: computing derivations through inferior takes twice as long
Date: Thu, 27 Jan 2022 09:50:07 +0100 [thread overview]
Message-ID: <87mtjhftq8.fsf@gnu.org> (raw)
In-Reply-To: <87czkeji4h.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 26 Jan 2022 22:32:02 +0100")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> I tried it in the GWL with the big RNAseq workflow I adopted from PiGx
> and the step to generate job scripts (which reference inferior packages)
> became considerably faster. There is still potential for improvement,
> but this change is the difference between not too bad (15 seconds) and
> unusable (> 5 minutes).
Good, that’s a step in the right direction.
I’ve sent in this issue a cleaned up patch series that achieves the same
result, plus some micro-optimizations. It’d be great if you could
confirm it still works for you.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-01-27 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 21:07 bug#48007: computing derivations through inferior takes twice as long Ricardo Wurmus
2022-01-26 20:51 ` Ludovic Courtès
2022-01-26 21:32 ` Ricardo Wurmus
2022-01-27 8:50 ` Ludovic Courtès [this message]
2022-01-27 9:56 ` Ricardo Wurmus
2022-01-27 13:33 ` Ludovic Courtès
2022-01-27 8:47 ` bug#48007: [PATCH 1/4] inferior: Create the store proxy listening socket only once Ludovic Courtès
2022-01-27 8:47 ` bug#48007: [PATCH 2/4] inferior: Keep the store bridge connected Ludovic Courtès
2022-02-18 11:30 ` bug#48007: computing derivations through inferior takes twice as long Ludovic Courtès
2022-01-27 8:47 ` bug#48007: [PATCH 3/4] inferior: Inferior caches store connections Ludovic Courtès
2022-01-27 8:47 ` bug#48007: [PATCH 4/4] inferior: Move initialization bits away from 'inferior-eval-with-store' 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=87mtjhftq8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=48007@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).