SourceTree 2.0 is horribly slow and not scaling well on Windows 10

[Vladimir Cascarade]

Thanks @sschilz. With your suggestion SourceTree has improved performance by a ton. I'm on W10

[Sandip Kumar]

 I can comment on the time spent complain you have because of huge processing times

Change the following two settings and see huge improvement:

- Tools > Options > General > Repo Settings - Set the Log rows to fetch per load to "0"

- tools> options> git - check the checkbox for "Disable LibGit2 integration"

Problem solved.

[Marco Del Valle]

So far so good! Got it up and running in less than 15 minutes, compared to 3 hours this morning and 1 hour last night trying to get SourceTree to push a 20-line commit.

It's a shame, because I was already used to the ST layout, but sometimes you have to learn to let go.

[Henry Poyntz]

I've been using GitKraken for the last two months now. You won't look back! haha.

[Marco Del Valle]

Two reasons why I won't be using Sourcetree anymore:

Can't add a new repository:

 

I spend most of my Git-Push time staring at spinning icons, "Loading" and "Not Responding":

 

I've tried every solution suggested in this thread, and even started with a clean install (Including removing all settings files). Time to give GitKraken a shot.

[Gianluca Ghettini]

tt

[Henry Poyntz]

It helped for a while, but I ended up buying GitKracken because it was still waaaaay to slow. https://www.gitkraken.com/

[Doug Rosenfeld]

Here is the official bug: SRCTREEWIN-7374

[Doug Rosenfeld]

Here are a few tips that have gotten the insanely slow 2.0 working better for me on Windows 7:

1. Use embedded Git (Tools > Options > Use Embedded Git)
2. Disable LibGit2 integration (Tools > Options > Disable LibGit2 integration)
3. Run SourceTree as Administrator

Hope this helps. 

[Doug Rosenfeld]

Ana - do you have a bug for the slowness in 2.0?

[lpd]

Thank you so much, the startup seemed a little slower but I'm no longer twiddling my thumbs for 10s after every action.

[kijvyn]

I confirm, doing this makes a HUGE difference.

[Henry Poyntz]

For anyone finding this thread - disable the libgit2 integration (using the checkbox you can see in the above post by Doug Ayers. This sped it up for me.

[douglascayers]

On Windows 10 x64 with SourceTree v2.1.11.0 I the app was slow for me too. Would take 3-5 seconds or more for SourceTree to scan and detect file changes even in small repos with only a hundred text files of 300 lines or less each. Trying to open another bookmarked repo would sometimes freeze the app entirely.

I then noticed that the embedded Git version was out of date so I updated it and after restarting SourceTree now everything is snappy again.

Coincidence or perhaps related to this conversation, worth a shot to make sure not only is SourceTree current but the embedded Git is current too.

Tools > Options > Git

[joedoe]

understand you pretty well - as SourceTree is unusable now i switched to shell now knowing much more then simple 'git push' or 'git commit -m' commands

[RJ Bates]

I'm in the same boat as the rest of you. I loved sourcetree until v2 now it is a total waste of time. I use submodules and need multiple repos open at the same time. I can't take the slowness anymore! Please fix Atlassian! Why no comments from an Atlassian Team member on this issues?

[Nelson Caballero-Olave]

I have to change my opinion.

After a few days of use it started to behave like before, but even worse... I installed in a new PC to work.  Its even slower than the other PC I used before and have it installed before.

In this new PC, even I save my user/password, it keeps popping a windows to re-authenticate :-(  and it takes about 20 to 30 seconds each interaction with the application.  The app just updated today to 2.1.11.0 and its even worse I think.

Guess I'll revert back to 1.x releases.  At this moment 2.x is more or less useless.  Please Atlassian fix it, IMO was the best git client all-around.

Ciao,

[Royd Amias]

I'm a Windows user and have hesitated to upgrade beyond Version 1.8.3.0. Everyone else on my team took the leap to 2.0+ and have regretted it. I kept the 1.8.3.0 around to fall back to just in case anyone else here needed it. Some did go back to that version while others went on to SmartGit.

[Oliver Gärtner]

I agree with the comments here. Sourcetree is a great app and 2.* is still working well on a Mac. On Windows however it is so slow that it basically became impossible to do work with it. A fix would be greatly appreciated.

[Jérémie Faucher-Goulet]

Agreed! This is why I'm using it right now on day-to-day, even worth paying for it. In our shop, SourceTree has simply become unusable.

But if Atlassian manages to fix their performance issues, I'll switch back in a hearthbeath. I miss it.

[Jérémie Faucher-Goulet]

- Cannot discard changes on dirty submodules (even though the option is offered)

- Half the time, discarding changes on a submodule will fail.

- No automatic "git sumodule update --init --recursive" when checking out a different commit

- Very picky on checkout if there are unstaged changes, auto-stahsing will often fail. (I would prefer no auto-stashing thank you)

- Merge and fast-forward will often fail, have to issue "git merge" on the command line

- Corrupting my git index if I do an interactive rebase while GitKraken is still running in the background (some of the times)

- "git gc" starts to issue "Unlink of file xxxxx failed. Should I try again?" after a while. Perhaps due to corruption?

- Cannot multi-select files, then click "Stage changes". Have to do every files one-by-one

- Why, why why not provide the option of using "System Git"? Seems like it would solve many issues

- Switching between repoisotories takes more time because it needs to reload (vs Tabs in SourceTree)

- No visibility/distinction between author and commiter. Which am I shown?

- No visibility/distinction betwen authored and commited. Which am I shown?

- I have yet to understand how to select the remote to Push to when there is more than one.

- Cannot change the scope of the diff displayed, What if I want 20 lines around? All the file?

- You'll probably laugh at this one, but I've yet found a simple way to copy (put in the pastebin) the name of a branch for pasting elsewhere. Currently I have to "Alt+T" and copy the command invite from the bash console.

- Needs better integration with external diff tools.

- "git flow" support? I haven't seen the equivalent of "Start Feature", "Start Release", etc. that SourceTree has. Seems to be lacking too.

- I don't like the way branches are displayed, using an horizontal line instead of diagonal like a "Y". Seems like my eyes have to work harder to understand the graph.

- I could probably go on for a while still....

 ---------------

There are 2 thing I will applaud GitKraken for however, because it does better than SourceTree:

1. Squash. Just select commits and right-click. Now if only it would not fail for no apparent reasons some of the times...

2. LINUX SUPPORT!!!!

[Assimilater]

"Lacking a lot of stuff" like what? It handles submodules, remote tracking, fast forward, hunk and line staging really well. Git flow works well as well. What else does sourcetree have?

I've never had crashes with git kraken, the only issues I've had is in relation to direct authentication/integration with Github gitlab etc. But setup the remote of a repository and it's fine.

[Jérémie Faucher-Goulet]

Lacking a lof of stuff that I use in SourceTree... And GitKraken still is very unstable (crashes, git corruption, failures to do simple operations). It is still a very new tool with all it's quirks that will get smoothed out over time (I hope).

But with all it's flaws, at least it's usable alongside the CLI. But would still prefer to use SourceTree.

[Mike Klein]

Another very unhappy user after 3-4 years being thrilled with the app.  The slowdown is at least 2 orders of magnitude.  I updated the embedded Git and clicked the "Disable LibGit2 integration" box in case.  Updating embedded Git helped (I had 2.8 previously), but not enough.  Now it's only about 1 order of magnitude slower than before.

It's absolutely awful and unusable as it is.  It's not an interactive tool anymore; it's batch.  Been struggling with it for a month or more, figuring updates would fix it, but nothing so far.

1.9.9.20 is a breath of fresh air in comparison, perfectly usable.

Windows 7 x64.

[Thomas Huijer]

Actually, I think the utter slowness of SourceTree 2.0 is wonderful, because it forced me to learn just about all the available git commandline options. Now I'm even faster than using SourceTree 1.x. ;-)

But seriously, the slowness is just killing my productivity. I've uninstalled 2.0. Unusable. Period.