Sourcetree using high CPU usage

[Doug Brandt]

We currently have a Windows 10 server that has Sourcetree running 24/7 that we use for deployment purposes only (PULL). It is a manual process that we "pull" the latest commits to a netshare location. It saves us time if we leave source tree running all the time.

My question is, the CPU is running high all day long because it is constantly looking for changes (and maybe other things). If i uncheck the option "Check default remotes for updates every ## minutes, will that make Source sit idle until we execute a PULL? Are there any other settings I should uncheck?

[Davide Bacchi]

I had a similar issue on a repo in what I later realized was a network folder.

In my case the issue was the git's git-fsmonitor--daemon that used the CPU to check on network drive and processes wern't killed properly.

I just disabled it: it takes a little longer to check for local edits when I open sourcetree but the CPU drain stopped.