For inboxes associated with an extindex (currently only the
special "all") one, we can share the git process across
all those inboxes unambiguously when retrieving full SHA-1
blobs.

The comment for my proposed patch is also out-of-date as that
git speedup has been a part of git since 2.33.
---
 lib/PublicInbox/GitAsyncCat.pm | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/lib/PublicInbox/GitAsyncCat.pm b/lib/PublicInbox/GitAsyncCat.pm
index 09744b34..f57e0336 100644
--- a/lib/PublicInbox/GitAsyncCat.pm
+++ b/lib/PublicInbox/GitAsyncCat.pm
@@ -9,11 +9,11 @@ our $GCF2C; # singleton PublicInbox::Gcf2Client
 
 sub ibx_async_cat ($$$$) {
        my ($ibx, $oid, $cb, $arg) = @_;
-       my $git = $ibx->{git} // $ibx->git;
+       my $isrch = $ibx->{isrch};
+       my $git = $isrch ? $isrch->{es}->git : ($ibx->{git} // $ibx->git);
        # {topdir} means ExtSearch (likely [extindex "all"]) with potentially
-       # 100K alternates.  git(1) has a proposed patch for 100K alternates:
-       # <https://lore.kernel.org/git/20210624005806.12079-...@80x24.org/>
-       if (!defined($ibx->{topdir}) && !defined($git->{-tmp}) &&
+       # 100K alternates.  git v2.33+ can handle 100k alternates fairly well.
+       if (!$isrch && !defined($ibx->{topdir}) && !defined($git->{-tmp}) &&
                ($GCF2C //= eval {
                require PublicInbox::Gcf2Client;
                PublicInbox::Gcf2Client::new();

Reply via email to