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
On my windows, the command git submodule status is very slow to cause the opening and refresh in sourcegit also slow.
Request:
For the git repo without submodule, I have a chance to add one setting in the .git/sourcegit.settings or from the GUI preference, to let sourcegit don't run the submodule status command.
Diagnostic messages from git by setting GIT_PERFORMANCE_TRACE=<path/to/log file>
For other tool, like vscode, it provides one option git.detectSubmodules, so I can set it to false to avoid submodule detecting.
BTW: I know the root cause of slow performance is not from sourcegit, and I didn't find any useful message from other places to improve the git submodule performance on windows, if someone knows, it will be great and thanks in advance.
The text was updated successfully, but these errors were encountered:
Problem status:
On my windows, the command
git submodule status
is very slow to cause the opening and refresh in sourcegit also slow.Request:
For the git repo without submodule, I have a chance to add one setting in the
.git/sourcegit.settings
or from the GUI preference, to let sourcegit don't run thesubmodule status
command.Diagnostic messages from git by setting
GIT_PERFORMANCE_TRACE=<path/to/log file>
So, it needs more than 12 and 9 seconds to finish 2 commands:
git ... submodule status
.I checked the source code of sourcegit, for now, there is no chance to ignore commands sequence from Repository.cs:
For other tool, like vscode, it provides one option
git.detectSubmodules
, so I can set it to false to avoid submodule detecting.BTW: I know the root cause of slow performance is not from sourcegit, and I didn't find any useful message from other places to improve the git submodule performance on windows, if someone knows, it will be great and thanks in advance.
The text was updated successfully, but these errors were encountered: