Too slow in the 'commit graph'

[diverger]

Description

Why after pushing the commits to the remote the UI won't reflect the changes immediately? Especially for large repos. Almost all ops related with UI are much slower then the CLI.

[justinrobots]

Hi @diverger, thanks for sending feedback. If you can send logs that capture this behavior we can investigate what may be causing these problems for you.

command: GitLens: Enable Debug Logging then restart VS Code
command: Developer: Export Logs and pick “GitLens” and “GitLens (Git)” logs

[diverger]

Just an example

[eamodio]

The log snippet doesn't really show much, since those are queries that get run as GitLens is discovering repositories and often those queries are much slower than normal, because there is often a lot going on during the discovery phase -- not only with GitLens and Git, but VS Code as well. Also we arbitrarily designate any Git call that takes over 1s as "slow" in the logs, to make it easier for us to look into issues, but there are MANY Git queries are will almost always take longer.

At the same The git rev-list --max-parents=0 HEAD -- call stands out as taking WAY too long and it is one that should generally be very fast. If you manually run git rev-list --max-parents=0 HEAD -- on your repository how long does it take?

Regardless, can you please provide logs that cover the issue(s) you reported.

Also the Commit Graph is also debounced to ensure we don't thrash Git when multiple changes are detected close together, which inherently adds a slight (~500ms) delay for repository changes and around ~1s for working tree changes

[diverger]

The CLI only take about 5s~6s. Then I tried run 'git gc', and reduce the commit history shown, it behave much better now.

[diverger]

Considering the several GB size of my repo, it seems the 'git gc' indeed can speed up the actions. So the bottle neck may in the git itself but not in gitlens.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.