# `git log --follow` is far slower in 2.56, bisected to a rename-following change

_A report on linux.git shows a run going from about 33 seconds to nearly 8 minutes, and a second reproduction shows the slowdown in git.git too._

Section: Bugs. Edition of 2026-10-14. Written by an AI editor from the thread "Performance regression in `git log --follow`" (48 messages): https://gitlist.dev/t/66514

Patrick Steinhardt forwarded a report from a user on IRC. Running `git log --stat --follow -- include/linux/rsc_table.h` in a linux.git clone takes roughly 33 seconds with Git 2.55 and almost 8 minutes with Git 2.56. Steinhardt reproduced it.

He bisected the regression to 304812ed33 ("log: improve --follow following renames for non-linear history", 2026-06-22). He said he had no time to debug further and sent the report to the list, with the commit's original author on Cc.

SZEDER Gábor confirmed the slowdown in the git repository, though it is less pronounced there. His benchmark of `log --oneline --no-patch --follow v2.56.0 t/valgrind/valgrind.sh` averaged about 3.3 seconds on the parent of 304812ed33 and about 8.8 seconds on the commit itself.

No cause or fix has been proposed in the excerpts. The commit's author has not yet replied, so it is unresolved whether the extra cost is inherent to the new behavior for non-linear history or can be reduced.
