mirror of
https://github.com/git/git.git
synced 2024-12-27 10:44:37 +08:00
a643157d5a
When `git repack -A -d` is run in a partial clone, `pack-objects`
is invoked twice: once to repack all promisor objects, and once to
repack all non-promisor objects. The latter `pack-objects` invocation
is with --exclude-promisor-objects and --unpack-unreachable, which
loosens all objects unused during this invocation. Unfortunately,
this includes promisor objects.
Because the -d argument to `git repack` subsequently deletes all loose
objects also in packs, these just-loosened promisor objects will be
immediately deleted. However, this extra disk churn is unnecessary in
the first place. For example, in a newly-cloned partial repo that
filters all blob objects (e.g. `--filter=blob:none`), `repack` ends up
unpacking all trees and commits into the filesystem because every
object, in this particular case, is a promisor object. Depending on
the repo size, this increases the disk usage considerably: In my copy
of the linux.git, the object directory peaked 26GB of more disk usage.
In order to avoid this extra disk churn, pass the names of the promisor
packfiles as --keep-pack arguments to the second invocation of
`pack-objects`. This informs `pack-objects` that the promisor objects
are already in a safe packfile and, therefore, do not need to be
loosened.
For testing, we need to validate whether any object was loosened.
However, the "evidence" (loosened objects) is deleted during the
process which prevents us from inspecting the object directory.
Instead, let's teach `pack-objects` to count loosened objects and
emit via trace2 thus allowing inspecting the debug events after the
process is finished. This new event is used on the added regression
test.
Lastly, add a new perf test to evaluate the performance impact
made by this changes (tested on git.git):
Test HEAD^ HEAD
----------------------------------------------------------
5600.3: gc 134.38(41.93+90.95) 7.80(6.72+1.35) -94.2%
For a bigger repository, such as linux.git, the improvement is
even bigger:
Test HEAD^ HEAD
-------------------------------------------------------------------
5600.3: gc 6833.00(918.07+3162.74) 268.79(227.02+39.18) -96.1%
These improvements are particular big because every object in the
newly-cloned partial repository is a promisor object.
Reported-by: SZEDER Gábor <szeder.dev@gmail.com>
Helped-by: Jeff King <peff@peff.net>
Helped-by: Jonathan Tan <jonathantanmy@google.com>
Signed-off-by: Rafael Silva <rafaeloliveira.cs@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
43 lines
848 B
Bash
Executable File
43 lines
848 B
Bash
Executable File
#!/bin/sh
|
|
|
|
test_description='performance of partial clones'
|
|
. ./perf-lib.sh
|
|
|
|
test_perf_default_repo
|
|
|
|
test_expect_success 'enable server-side config' '
|
|
git config uploadpack.allowFilter true &&
|
|
git config uploadpack.allowAnySHA1InWant true
|
|
'
|
|
|
|
test_perf 'clone without blobs' '
|
|
rm -rf bare.git &&
|
|
git clone --no-local --bare --filter=blob:none . bare.git
|
|
'
|
|
|
|
test_perf 'checkout of result' '
|
|
rm -rf worktree &&
|
|
mkdir -p worktree/.git &&
|
|
tar -C bare.git -cf - . | tar -C worktree/.git -xf - &&
|
|
git -C worktree config core.bare false &&
|
|
git -C worktree checkout -f
|
|
'
|
|
|
|
test_perf 'fsck' '
|
|
git -C bare.git fsck
|
|
'
|
|
|
|
test_perf 'count commits' '
|
|
git -C bare.git rev-list --all --count
|
|
'
|
|
|
|
test_perf 'count non-promisor commits' '
|
|
git -C bare.git rev-list --all --count --exclude-promisor-objects
|
|
'
|
|
|
|
test_perf 'gc' '
|
|
git -C bare.git gc
|
|
'
|
|
|
|
test_done
|