nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SourceTree takes 3 seconds to stage/unstage a file

Graham Borland

Staging or unstaging a file takes almost 3 seconds. This is on a top-end late-2013 Macbook Pro.

It doesn't make a difference if it's done from the menu or by double-clicking.

It's the same whether it's adding a new file, or staging changes to an existing file. Even a few lines changed in a modestly-sized file (few hundred lines) exhibits this.

I do not have any untracked files.

I tried changing the view filter from "Show Pending" to "Show Modified" and that didn't help either; if anything it made it worse (5 seconds!).

How can I improve this?

SourceTree 1.8.1, using embedded Git.

Macbook Pro, OS X 10.9.1, 2.6GHz Core i7, 16GB RAM

Accepted answers

All comments

Adrian Moerchen

How long does git stash on the shell need? At least on Windows SourceTree only invokes shell commands.

Graham Borland

git add or git stash on the command line are both instantaneous. This delay is definitely coming from Sourcetree rather than Git. To further describe what I see:

A dialog pops up saying "Staging files". This disappears after about half a second.

Two little round spinning progress indicators pop up; one in the working tree, and one in the index. These spin round for 2 or 3 seconds.

The file in question finally disappears from the working tree and reappears in the index area. After the file has appeared in the index, the two little spinners start spinning again for another second or two.

Once the spinners stop for the second time, then Sourcetree settles down and I can continue working. The overall process is at least 3 seconds.

Seth

You mentioned you have no untracked files, and you are staging relatively small changes. What about your repository itself? How big is it?

Graham Borland

Total size = 32M

.git = 1.6M

Size of tracked files = 5M

(Ignored files 27M approx)

Total number of files (including .git) = 614

Seth

Not very big, then. The only other good reason I can think of would be if your repository wasn't on a local, internal drive. I would expect a little lag or slowness from a flash drive or network storage.

Graham Borland

Right. It's all local, on the internal SSD. And as I mentioned, the equivalent git commands in the shell execute instantaneously.

Seth

An SSD even. I can't think of any good reason for SourceTree to take that long. Hopefully you get some attention from Atlassian on this.

fuck atlassian

Years go by they are still not bating an eye. Great company, if only i had simple alternative i would abandon this trashware this instant.

Seth

https://git-scm.com/downloads/guis

fuck atlassian

also this - https://www.plasticscm.com will give it a shot, friend suggested

fuck atlassian

http://www.npackd.org/p/com.sourcetreeapp.SourceTree/1.5.2 ive read people recommending to use this old version, im trying it now, it may fix problems introduced by unable coders in latest versions.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

sourcetree