t/perf: time rev-list with UNINTERESTING commits

We time a straight "rev-list --all" and its "--object" counterpart, both going all the way to the root. However, we do not time a partial history walk. This patch adds an extreme case: a walk over a very small slice of history, but with a very large set of UNINTERESTING tips. This is similar to the connectivity check run by git on a small fetch, or the walk done by any pre-receive hooks that want to check incoming commits. This test reveals a performance regression in git v1.8.4.2, caused by fbd4a70 (list-objects: mark more commits as edges in mark_edges_uninteresting, 2013-08-16): Test fbd4a703^ fbd4a703 ------------------------------------------------------------------------------------------ 0001.1: rev-list --all 0.69(0.67+0.02) 0.69(0.68+0.01) +0.0% 0001.2: rev-list --all --objects 3.47(3.44+0.02) 3.48(3.44+0.03) +0.3% 0001.4: rev-list $commit --not --all 0.04(0.04+0.00) 0.04(0.04+0.00) +0.0% 0001.5: rev-list --objects $commit --not --all 0.04(0.03+0.00) 0.27(0.24+0.02) +575.0% Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Jeff King committed Jan 20, 2014 at 21:25 UTC ea97002fc9f682a804ac05212d069e38fa3e365c
1 file changed +12
t/perf/p0001-rev-list.sh
+12
@@ -14,4 +14,16 @@ test_perf 'rev-list --all --objects' '
14 git rev-list --all --objects >/dev/null
15 '
16
17 +test_expect_success 'create new unreferenced commit' '
18 + commit=$(git commit-tree HEAD^{tree} -p HEAD)
19 +'
20 +
21 +test_perf 'rev-list $commit --not --all' '
22 + git rev-list $commit --not --all >/dev/null
23 +'
24 +
25 +test_perf 'rev-list --objects $commit --not --all' '
26 + git rev-list --objects $commit --not --all >/dev/null
27 +'
28 +
29 test_done