Source Tree Slowness, Almost Unuseabe

[PlanningDev]

Is Source Tree extemely slow on Windows? My git repo's are out on servers so they are mapped through the network but even while plugged in at work its super slow. 5-10 min to refresh the repo changes. 5 min commit times, staging is the same.

[stevestreeting · Accepted solution]

Git's speed comes largely from the fact that everything is a local operation - by putting your repository on a remote drive you're completely eliminating that advantage so it's not a good idea. Run your repo locally and push to your server instead when you want to share.

[PlanningDev]

I figured that was the case. However the problem I have is that I am using GIT in a scenario where the files are developed/controlled by another program (IBM Cognos TM1). My goal is simply to use GIT as a way to see code change within that directory and track the changes to issues in JIRA using Stash and Fisheye. Unfortunately this means I can't setup GIT the way a true software development process would work. Im going to see if I can put sourcetree directly on the server that our software runs as most of our developers use Remote Desktop and develop from there anyway.

[stevestreeting]

OK, just to make you aware another alternative to remote desktop is to pull changes from the server repo into a local repo so you can look at them, or to use a post-commit hook on that server repo to automatically push those changes somewhere else.

[PlanningDev]

Looks like GIT GUI is also slow from my own machine. This must be related to WAN.

[PlanningDev]

I was using the system git. The speed really isnt any better either way. Using the GIT GUI on the server that git is running is superfast. Almost no delay. Using source tree from my system is slow.

[Malik]

Is your SourceTree instance using embedded git or system git. Then if you try with one of this git directly from command link, is it also slow?