From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <derrickstolee@github.com>,
Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/7] pack-revindex: enable on-disk reverse indexes by default
Date: Mon, 10 Apr 2023 18:53:18 -0400 [thread overview]
Message-ID: <cover.1681166596.git.me@ttaylorr.com> (raw)
This series enables pack reverse-indexes to be written to disk by
default instead of computed on-the-fly in memory.
For repositories with large packs, this can have a significant benefit
for both end-users and Git forges. Extensive performance tests appear in
the fifth and sixth commit, but here are some highlights:
- The time it takes to generate a pack containing objects for the 10
most-recent commits in linux.git (starting from 68047c48b228) drops
from ~540ms to ~240ms, yielding a ~2.22x improvement.
- The time it takes to compute the on-disk object size of a single
object drops from ~300ms to 4ms, yielding a ~76.96x improvement.
Reverse indexes are a trade-off between the time they take to be
computed versus the time it takes to access a single record. In-memory
reverse indexes take time to generate proportional to the number of
packed objects in the repository, but have instantaneous lookup time.
On-disk reverse indexes can be "generated" instantly (the time it takes
to generate them is a one-time cost, loading them is instantaneous).
But individual record lookup time is slower, since it involves multiple
disk I/O operations.
In the vast majority of cases, this trade-off favors the on-disk ".rev"
files. But in certain cases, the in-memory variant performs more
favorably. Since these cases are narrow, and performance is machine- and
repository-dependent, this series also introduces a new configuration
option to disable reading ".rev" files in the third commit.
The series is structured as follows:
- A couple of cleanup patches to plug a leak in stage_tmp_packfiles().
- Three patches to enable `pack.readReverseIndex`.
- Another patch to change the default of `pack.writeReverseIndex` from
"false" to "true".
- A final patch to enable the test suite to be run in a mode that does
not use on-disk ".rev" files.
Thanks in advance for your review. I'm really excited to get this in the
hands of users after a couple of years of running this at GitHub (and
being opt-in otherwise).
Taylor Blau (7):
pack-write.c: plug a leak in stage_tmp_packfiles()
t5325: mark as leak-free
pack-revindex: make `load_pack_revindex` take a repository
pack-revindex: introduce GIT_TEST_REV_INDEX_DIE_ON_DISK
pack-revindex: introduce `pack.readReverseIndex`
config: enable `pack.writeReverseIndex` by default
t: invert `GIT_TEST_WRITE_REV_INDEX`
Documentation/config/pack.txt | 8 +++++++-
builtin/index-pack.c | 5 +++--
builtin/pack-objects.c | 5 +++--
ci/run-build-and-tests.sh | 1 -
pack-bitmap.c | 5 +++--
pack-revindex.c | 12 +++++++++---
pack-revindex.h | 6 ++++--
pack-write.c | 2 ++
packfile.c | 2 +-
repo-settings.c | 1 +
repository.h | 1 +
t/README | 2 +-
t/perf/p5312-pack-bitmaps-revs.sh | 3 +--
t/t5325-reverse-index.sh | 16 +++++++++++++++-
14 files changed, 51 insertions(+), 18 deletions(-)
--
2.40.0.323.g9c80379958
next reply other threads:[~2023-04-10 22:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 22:53 Taylor Blau [this message]
2023-04-10 22:53 ` [PATCH 1/7] pack-write.c: plug a leak in stage_tmp_packfiles() Taylor Blau
2023-04-11 13:23 ` Derrick Stolee
2023-04-11 21:25 ` Taylor Blau
2023-04-10 22:53 ` [PATCH 2/7] t5325: mark as leak-free Taylor Blau
2023-04-10 22:53 ` [PATCH 3/7] pack-revindex: make `load_pack_revindex` take a repository Taylor Blau
2023-04-11 13:45 ` Derrick Stolee
2023-04-11 21:30 ` Taylor Blau
2023-04-12 17:33 ` Derrick Stolee
2023-04-10 22:53 ` [PATCH 4/7] pack-revindex: introduce GIT_TEST_REV_INDEX_DIE_ON_DISK Taylor Blau
2023-04-10 22:53 ` [PATCH 5/7] pack-revindex: introduce `pack.readReverseIndex` Taylor Blau
2023-04-10 22:53 ` [PATCH 6/7] config: enable `pack.writeReverseIndex` by default Taylor Blau
2023-04-13 16:14 ` Junio C Hamano
2023-04-10 22:53 ` [PATCH 7/7] t: invert `GIT_TEST_WRITE_REV_INDEX` Taylor Blau
2023-04-11 13:51 ` Derrick Stolee
2023-04-11 21:33 ` Taylor Blau
2023-04-12 17:37 ` Derrick Stolee
2023-04-11 13:54 ` [PATCH 0/7] pack-revindex: enable on-disk reverse indexes by default Derrick Stolee
2023-04-11 21:40 ` Taylor Blau
2023-04-12 17:39 ` Derrick Stolee
2023-04-12 22:20 ` [PATCH v2 " Taylor Blau
2023-04-12 22:20 ` [PATCH v2 1/7] pack-write.c: plug a leak in stage_tmp_packfiles() Taylor Blau
2023-04-12 22:20 ` [PATCH v2 2/7] t5325: mark as leak-free Taylor Blau
2023-04-12 22:20 ` [PATCH v2 3/7] pack-revindex: make `load_pack_revindex` take a repository Taylor Blau
2023-04-12 22:20 ` [PATCH v2 4/7] pack-revindex: introduce GIT_TEST_REV_INDEX_DIE_ON_DISK Taylor Blau
2023-04-12 22:20 ` [PATCH v2 5/7] pack-revindex: introduce `pack.readReverseIndex` Taylor Blau
2023-04-12 22:20 ` [PATCH v2 6/7] config: enable `pack.writeReverseIndex` by default Taylor Blau
2023-04-12 22:20 ` [PATCH v2 7/7] t: invert `GIT_TEST_WRITE_REV_INDEX` Taylor Blau
2023-04-13 13:40 ` [PATCH v2 0/7] pack-revindex: enable on-disk reverse indexes by default Derrick Stolee
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=cover.1681166596.git.me@ttaylorr.com \
--to=me@ttaylorr.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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.
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 NNTP newsgroup(s).