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; } } }

Source Tree 1.5.6 (App Store) is very slow after hg pull+update

Bi11

After hg repo pull+update, view log is very slow to be updated.

Active Monitor shows 10+ python processes consumes full CPU.

On my MacBook Air, Source Tree usually takes 3~5s to display log view, about 10s to fully display diffs. It is slow but acceptable.

After pull+update dialog closed, Source Tree need 30s+ to make log view updated.

Source Tree 1.5.6 (App Store)

Mac OS X 10.8.2

MacBook Air 11-inch Late 2010, 1.4G Core 2 Duo, 4G DDR3, 64G SSD.

Accepted answers

Bi11

I finally make my Source Tree works fast!

The trick is to use System Mercurial instead of Embedded Mercuial!

Embedded version is 2.2.2

My current hg version is 2.2.3+20120707

Now Source Tree only takes 1 to 3s on my MacBook Air when the log view refreshed. Sweet!

All comments

stevestreeting

I'm working on a 2010 i5 MBP with a non-SSD drive and cannot reproduce this. Speed after pulling is no different to any other time here, average just under 2s. Repo size is ~400MB.

A few things that might affect this:

Disk space free. OS X becomes considerably less efficient when you're below about 15GB or 10%, because its dynamic defragmentation cannot function as effectively when you're below this.
Subrepositories. Do you have any in this repo?
Python version. Have you replaced the system Python version with a different one? SourceTree precompiles all the Mercurial scripts for Python 2.7, the default on Lion and Mountain Lion. The Mac App Store version cannot save compiled code, so if you've set a different global Python version you should switch to using a system-installed version of Mercurial which can have its Python precompiled and saved.

Bi11

My repo is very simple and only about 100 logs, 3MB in total.

I just opened Source Tree, first open log view only 2s, after pull+update, it takes 14s.

1 Disk free space more than 5G.

2 No subrepos

3 No system file change.

The only bottleneck is my CPU. The 10 more python processes started after pull+update are nesscary? That takes a lot time with full CPU usage.

stevestreeting

FYI, 5GB is under the recommended free space for OS X. 15GB / 10% is the recommended minimim for optimal performance. I've seen several of 1st gen MBAs have issues when they're low on free space.

Building the SourceTree views takes a few different hg calls, especially the log view. I wouldn't have thought it was 10, but I guess that's possible. On my 2010 MBP I only ever see 1 or 2 in Activity Monitor, my guess is that due to the performance issues caused by low disk space they're clogging up.

The fact that it happens just after Pull and at no other time also suggests disk issues. The refresh tasks after Pull are completely identical to the tasks when first opening the repo, since it has to build the same visual state. I think it's particularly slow for you after Pull because that's changed files on disk, which has caused the OS X disk management to kick in, and it's slow because it doesn't have enough free space to work efficiently.

Bi11

I've tested another small repo with only pull one change set with one file changes.

In terminal, hg pull -u finished immediatly after pulling from remote server.

I striped the change set and tested again.

In source tree, refresh after pull, takes 5s; refresh after update, takes 5s; refresh after pull+update, takes 10s.

I think the log refresh takes a long time on my MacBook Air, and after pull+update, it takes 2x time.

Bi11

I tested on another Mac, it's takes 5s to do a log view refresh.

Mac mini (Mid 2011) 2.3 Core i5, 4G memory.

406G Disk Free Space, Repo 300M.

Hg works fast, but Source Tree log view refresh if very slow (after commit, update, pull, etc.).

Bi11

I finally make my Source Tree works fast!

The trick is to use System Mercurial instead of Embedded Mercuial!

Embedded version is 2.2.2

My current hg version is 2.2.3+20120707

Now Source Tree only takes 1 to 3s on my MacBook Air when the log view refreshed. Sweet!

Bi11

On another Mac Mini, change to System Mercurial (2.2.2+20120602) also makes Source Tree much faster. And now it only takes 1 to 2s to do the log view refresh too.

stevestreeting

Glad you've got it working. This was my suggestion in point 3 of my original reply

Bi11

Is it not cause by the difference of hg version, but python version?

I remebered that I was using Source Tree which is not from App Store, and I registered it (free). but I changed to App Store version because it is slow. After changed to App Store version, there is no difference, may be even slower, that made me to post a question here. :-(

My /usr/bin/python is 2.7.2.

My Mac OS was updated from 10.6 to 10.7 and now 10.8. Under /usr/bin/, there is python2.5, python2.6 and python2.7, linked to Python.framework. But /usr/bin/python is none of them.

$ /usr/bin/python2.7
Python 2.7.2 (default, Jun 20 2012, 16:23:33)
[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin

$ /usr/bin/python
Python 2.7.2 (default, Jun 20 2012, 16:23:33)
[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin

MD5 (/usr/bin/python) = d715a9f1baf67f04265b385ae43fb503
MD5 (/usr/bin/python2.7) = f04e60346870d7c834352eb58beb1fb8

32 -rwxr-xr-x 2 root wheel 58896 Jul 28 00:47 /usr/bin/python
8 lrwxr-xr-x 1 root wheel 75 Jul 28 00:47 /usr/bin/python2.7 -> ../../System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7

16 -rwxr-xr-x 1 root wheel 35120 Jul 28 00:47 /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7

Wired.

Welcome!

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

Quick Links

Find more posts tagged with

sourcetree