about summary refs log tree commit homepage
path: root/script
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2023-04-22 10:33:42 +0000
committerEric Wong <e@80x24.org>2023-04-22 19:33:08 +0000
commit10f31b26e010243ab919dbafeb6f95c6e30640e9 (patch)
treefa793044a409f009c69d741bf34fb4ea42f9178a /script
parentc23413abbe1db6e96af4a028f69613d1340e880c (diff)
downloadpublic-inbox-10f31b26e010243ab919dbafeb6f95c6e30640e9.tar.gz
With my partial git.kernel.org mirror, this brings a full prune
down from ~75 minutes to under 5 minutes using git 2.19+.  This
speedup even applies to users on slow storage (rotational HDD).

First off, xapian-delve(1) is nearly 10x faster for dumping
boolean terms by prefix than the equivalent Perl code with
Xapian bindings.  This performance difference is critical since
we need to check over 5 million commits for pruning a partial
git.kernel.org mirror.

We can use sed(1) and sort(1) to massage delve output into
something suitable for the first comm(1) input.

For the second comm(1) input, the output of `git cat-file
--batch-check --batch-all-objects' against all indexed git repos
with awk(1) filtering provides the necessary output for
generating a list of indexed-but-no-longer accessible commits.

sed(1) and awk(1) are POSIX standard tools which can be roughly
2x faster than equivalent Perl for simple filters, while
sort(1) is designed to handle larger-than-memory datasets
efficiently (unlike the `sort' perlop).

With slow storage and git <2.19, the switch to --batch-all-objects
actually results in a performance regression since having git
perform sorting results in worse disk locality than the previous
sequential iteration by Xapian docid.  git 2.19+ users with
`--unordered' support benefits from improved storage locality;
and speedups from storage locality dwarfs the extra overhead of
an extra external sort(1) invocation.

Even with consumer-grade SATA-II SSDs, the combo of --unordered
and sort(1) provides a noticeable speedup since SSD latency
remains a factor for --batch-all-objects.

git <2.19 users must upgrade git to get acceptable performance
on slow storage and giant indexes, but git 2.19 was released
nearly 5 years ago so it's probably a reasonable requirement for
performance.

The only remaining downside of this change for all users
the extra temporary disk space for sort(1) and comm(1);
but the speedup provided with git 2.19+ is well worth it.
Diffstat (limited to 'script')
-rwxr-xr-xscript/public-inbox-cindex1
1 files changed, 1 insertions, 0 deletions
diff --git a/script/public-inbox-cindex b/script/public-inbox-cindex
index 4c9136cf..2f7796e7 100755
--- a/script/public-inbox-cindex
+++ b/script/public-inbox-cindex
@@ -29,6 +29,7 @@ GetOptions($opt, qw(quiet|q verbose|v+ reindex jobs|j=i fsync|sync! dangerous
                 indexlevel|index-level|L=s
                 batch_size|batch-size=s max_size|max-size=s
                 project-list=s exclude=s@
+                sort-parallel=s sort-compress-program=s sort-buffer-size=s
                 d=s update|u scan! prune dry-run|n C=s@ help|h))
         or die $help;
 if ($opt->{help}) { print $help; exit 0 };