summaryrefslogtreecommitdiff
path: root/t/perf
diff options
context:
space:
mode:
authorVictoria Dye <vdye@github.com>2021-11-29 15:52:43 (GMT)
committerJunio C Hamano <gitster@pobox.com>2021-11-29 20:51:26 (GMT)
commitf2a454e0a5e26c0f7b840970f69d195c37b16565 (patch)
treec7eaaed27d6fa8a413ef42c7805a28d8fe087a3d /t/perf
parent4d1cfc1351ffec47bba1318e9cd1ed13c5182951 (diff)
downloadgit-f2a454e0a5e26c0f7b840970f69d195c37b16565.zip
git-f2a454e0a5e26c0f7b840970f69d195c37b16565.tar.gz
git-f2a454e0a5e26c0f7b840970f69d195c37b16565.tar.bz2
unpack-trees: improve performance of next_cache_entry
To find the first non-unpacked cache entry, `next_cache_entry` iterates through index, starting at `cache_bottom`. The performance of this in full indexes is helped by `cache_bottom` advancing with each invocation of `mark_ce_used` (called by `unpack_index_entry`). However, the presence of sparse directories can prevent the `cache_bottom` from advancing in a sparse index case, effectively forcing `next_cache_entry` to search from the beginning of the index each time it is called. The `cache_bottom` must be preserved for the sparse index (see 17a1bb570b (unpack-trees: preserve cache_bottom, 2021-07-14)). Therefore, to retain the benefit `cache_bottom` provides in non-sparse index cases, a separate `hint` position indicates the first position `next_cache_entry` should search, updated each execution with a new position. Signed-off-by: Victoria Dye <vdye@github.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/perf')
0 files changed, 0 insertions, 0 deletions