summaryrefslogtreecommitdiff
path: root/t/t1021-rerere-in-workdir.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2019-09-07 01:04:40 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-09-09 10:56:50 -0700
commitdd2e50a84ea431a6cec69f37251f29bf3cfcbb68 (patch)
tree665279f4126028df11932b2e584ed21c26ebe629 /t/t1021-rerere-in-workdir.sh
parentcommit-graph: don't show progress percentages while expanding reachable commits (diff)
downloadtgif-dd2e50a84ea431a6cec69f37251f29bf3cfcbb68.tar.xz
commit-graph: turn off save_commit_buffer
The commit-graph tool may read a lot of commits, but it only cares about parsing their metadata (parents, trees, etc) and doesn't ever show the messages to the user. And so it should not need save_commit_buffer, which is meant for holding onto the object data of parsed commits so that we can show them later. In fact, it's quite harmful to do so. According to massif, the max heap of "git commit-graph write --reachable" in linux.git before/after this patch (removing the commit graph file in between) goes from ~1.1GB to ~270MB. Which isn't surprising, since the difference is about the sum of the uncompressed sizes of all commits in the repository, and this was equivalent to leaking them. This obviously helps if you're under memory pressure, but even without it, things go faster. My before/after times for that command (without massif) went from 12.521s to 11.874s, a speedup of ~5%. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t1021-rerere-in-workdir.sh')
0 files changed, 0 insertions, 0 deletions