You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work on a large repo, and Found that show commit is very slow. I profile vim and found the time cost on git ls-tree, which take several seconds on each call, and is called by fugitive#filereadable, and which is called from other plugin like vim-projectionist, vim-bundler, vim-rails, . following is a profile on show commit from status window:
As filereadable is a common action to call from anywhere, this problem makes fugitive respond slowly, seriously affecting the user experience.
So my question is: can this performance be optimized to avoid getting the full tree? Or I have to find a way to adjust the caller and not call readable in the fugitive-related buffer?
The text was updated successfully, but these errors were encountered:
I work on a large repo, and Found that show commit is very slow. I profile vim and found the time cost on
git ls-tree
, which take several seconds on each call, and is called byfugitive#filereadable
, and which is called from other plugin likevim-projectionist
,vim-bundler
,vim-rails
, . following is a profile on show commit from status window:fugitive-profile.log
As filereadable is a common action to call from anywhere, this problem makes fugitive respond slowly, seriously affecting the user experience.
So my question is: can this performance be optimized to avoid getting the full tree? Or I have to find a way to adjust the caller and not call readable in the fugitive-related buffer?
The text was updated successfully, but these errors were encountered: