Long Version: Had this issue with large repository (has many files). Investigated and found root cause of SourceTree slowness. If you find git status -uall is super slow (same slowness as SourceTree then this is likely your culprit). Sourcetree always uses -uall when doing status refreshes.
We have compiled a list of solutions that reviewers voted as the best overall alternatives and competitors to SourceTree, including GitKraken Client, Git Tower, TortoiseHg, and Google Cloud Source Repositories.
Technically speaking, both are great GUI tools that provide a seamless way to contribute to projects on GitHub. Sourcetree provides a wider range of features than the GitHub's own GUI tool, and also gives you more control over your repositories. GitHub Desktop, however, is the best tool, if you are just using GitHub.
Navigate to C:\Users\<UserName>\AppData\Local and delete SourceTree & SourceTree-Settings folder. Navigate to C:\Users\<UserName>\AppData\Local\Atlassian and delete all SourceTree Files/Folder.
I know this is an old question, but you could also try this:
https://stackoverflow.com/a/24045966/371917
$ git config --global core.preloadindex true
$ git config --global core.fscache true
$ git config --global gc.auto 256
Secondly, here is a post that explains that git gc --aggressive
may not be a great idea.
Executing the stated git command did not do the trick for me. Eventually what really speed up SourceTree was disabling 'spell check commit messages' in the tools > options menu. I also disabled 'load avatar images from gravatar.com' option while I was at it.
Any action in my source tree was super slow. Commit, click on a file to see changes, push etc.
I discovered that my antivirus (avast) was the cause. I disabled the file protection and source tree became immediate.
I had this problem too. I also have avast and this worked for me and might work for you and maybe a different AV. But I added the C:\Users\YOURNAME\AppData\Local\Atlassian\ to my avast exclusions directory and now it is running much faster!
For me it was the 'spell check commit messages' option in the settings. Even clicking the tick took 20 sec to process, but it was the last freezing I experienced.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With