I watched this thread, but it seems to be focused on Windows 7 and not apply to me
https://answers.atlassian.com/questions/10413451/sourcetree-slow-in-windows-7-x64...
I've always found SourceTree to be very slow. Lately though, it's gotten out of hand. Especially since native git and GitX is orders of magnitude faster. What I mean by that is that the UI freezes a lot (I get the spinning bathing ball for many seconds). For instance, this happen when I click a file in the "Unstaged" area, so it's added to the "Staged" area. Now I have to wait a couple of seconds before I can click on a file in the "Unstaged" area again. Also just scrolling in the "Unstaged" area is very slow.
Some more information
This is really painful. Any way I can help out by sending dumps/more information?
I found a solution working for me:
I realized that SourceTree used the embedded git with version 2.1. I installed via brew git 2.3 and switched sourcetree to using my brew-git.
Tada: Now SourceTree is fast, again.
Steps:
I did this, seems to be faster so far. I'll post an update in a few days to see if it stick. Thank you Sebastian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update: Changes did not help after all. Still experience the same sluggishness.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Sebastian Gabbert, seems faster now
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another person here for whom this didn't work. Updated to the latest in brew and ran `brew link git` to get it to be the system defauld and still no effect on my spinning beachball outcomes on macOS.
For reference, my performance problems are all related to viewing diffs in history mode. Clicking on certain diffs just drives the app totally insane and it spins out for 30-60 seconds.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I use Sourcetree version 2.7.6 (177) on MacOS High Sierra and can confirm that it's still works extremely slow. Every action takes ages. Switching to use internal git, as suggested in above messages, doesn't change anything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same experience here, on Sierra. It's a sad fate for such a great tool.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
An update, since maybe I should not only complain...
SourceTree is running snappily for me right now with this combination:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you already try to restart your Mac? My SourceTree is fast (with my system's git), but after some time it's getting slower and slower. When I restart my system (mostly after a about a week), it's fast again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It was an "old" git repository and a simple `git fsck` from the command line boost Sourcetree performance.
I hope it also works for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you! I ended up just getting a new MacBook after which I was finally able to switch back from another app.
When I ran `git fsck` on my main repos there were TONS of output though! So maybe that was a big part of of my slowdown that made me move away from ST.
Recommend other long-haulers try this!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I updated my git via brew, from 2.17.2 to 2.19.1, and did the Use System Git thing, but was still SLOW!
Then, I realize that I didn't include some files to my gitignore, SO, SourceTree was going trough all my package-lock.json! And of course thousands and thousands of lines, seems to overload sourcetree when trying to identify the changes!,
Ignoring those files was the solution for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sourcetree should avoid making diff everytime on package-lock.json.
To avoid it but still include it in your repo, go to Preferences > Diff > Ignore File Patterns and add ", package-json.lock"
Source will ignore it except when commiting, which makes Sourcetree useable again, thanks to Mark Wylie.
It's a shame that SourceTree still has so much perf issues, easly fixable... But I surely won't do better so I'll keep my mouth shut down :*
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Going to Preferences > Diff > Ignore File Patterns and adding
, package-lock.json
Fixed the issue for me. Thanks, @QuentinNev and @JaimeMontero!
My question is, should this be the solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Told SourceTree to use local git version, restart SourceTree and nothing has changed. Then 2 minutes later it was slightly faster, and then again slow, but it's a bit less frequent.
It seems to me that SourceTree want to rescan the whole repo every time you click on something.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To anyone having a slow Sourcetree app in Mac, do the following:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe the problem is with the Git version. Try updating it to the last one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Upgraded git to 2.19.1 and use System Git (as I have set) seems now works better. I guess I'd need to work some time to justify performance improvements.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mine seems to be working now on my Mac. I've been seeing significant performance issues with SourceTree as well. Tried many things (including suggestions here) and it continued to be very slow.
I finally changed the view from 'log' to 'file status' and then back again and now it's speedy again. IU believe the UI might have a memory leak that gets reset upon view change(I know, doesn't make immediate sense). I'll post updates if things change.
Mo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
this worked for me, thanks for feeding back ;) atlassian, please fix!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've been having this issue quite a lot lately especially when I scroll down the commits scroll view. It'll chug for 0.5s every 10 or so commits I scroll down. It's extremely annoying.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, now I've tried this for some time. And the problem is really not fixed by that. And not restarting either. I get a LOT of bathing ball time. 10 seconds is not uncommon. As a comparison running git status from command line takes 0.15s.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply @Sebastian Gabbert. I think you're right. First it was even slower, but then I restarted Source Tree and now it's actually faster again. It seems something is fishy in ST as well though. Thanks for the advice!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
exactly the same here. Same Setup, same problems.
I've seen the spinning ball especially building the diff and staging large css-files for several seconds.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.