Fast Mac, new OSX, actual SourceTree - stage is very slow

[Macsis]

I'v actual version of SourceTree (1.7.3), very fast iMac (3,7GHz, SSD, 32Mb RAM), new OSX, but SourceTree works VERY slow.

The slowest is updated contents of the list of files (Files staged in the index AND Files in the working tre) that occurs every time then I stage / commit in all the dialogues. Each update takes up to 10 seconds.

Not a lot of changes, usually within a ten. The repository is not very big (about 9000 files in the main it is code and the image, the total volume of 2,5 Gb). Additionaly connected to two remote repository on BitBucket (original and fork on it).

The problem is serious for me, because I spend a lot of time to empty out. Is there a way to solve it?

[KieranA]

Hey there,

Sorry this is happening for you. Could you go through the following article so we could narrow down possible issues? https://confluence.atlassian.com/display/SOURCETREEKB/Troubleshooting+Performance+Problems+in+SourceTree

Thanks in advance

[Macsis]

Checklist

1. NO
2. I use EMBEDED GIT version 1.7.11.1
3. CPU: 3,7GHz, RAM: 32Gb, FusionDrive (free 400+ Gb)
4. i use SourceTree version 1.7.3
5. repository is local, on my hard disk
6. 'git log' is fast
7. NO

Information to provide to support

1. I use EMBEDED GIT version 1.7.11.1
2. CPU: 3,7GHz, RAM: 32Gb, FusionDrive (free 400+ Gb)
3. repository is local, on my hard disk + two connected
4. I have 6 repositories
5. 1.7.3
6. MAC OS 10.9
7. Show pending

[Macsis]

so what? ;)

[KieranA]

Sorry I haven't replied, you've been on my top list. Could you try out the latest version of SourceTree to see if that helps?

Thanks in advance

[Macsis]

At first glance, it became much faster. Work a couple of days and I will write a final conclusion.

[Rick Jensen]

I noticed major slowness in updating file statuses, but just upgraded to newest version (1.8.0.2) and things seem to be much faster. If I notice it getting slow again, I'll come back here. It's possible it's due to leaving it open for days / weeks at a time, which is how I usually use it :)