gitx icon indicating copy to clipboard operation
gitx copied to clipboard

Very slow to refresh with latest update (0.15.1949)

Open zoodor opened this issue 10 years ago • 5 comments

Recently updated to the latest version (0.15.1949) and the performance on the history view has dramatically deteriorated. Any time the the history view is refreshed it takes significantly longer than it did before the update (one of our repositories is now taking almost 10 seconds each refresh, when previously it would have been sub-second (I think, from memory)).

I am using OSX 10.7.5 and others on my team are on 10.9.2 and we are all seeing this performance degradation with the aforementioned update.

zoodor avatar Aug 05 '14 10:08 zoodor

I also notice that GitX using ~200% CPU when I'm running a build, which executes a FS-intensive process in a directory listed in .gitignore. Seems like this may be a related issue.

millerdev avatar Aug 07 '14 02:08 millerdev

I am experiencing the same performance problems with refreshing the view (⌘R) after upgrading to v0.15.1949. I’m using OS X 10.9.4.

bquorning avatar Aug 12 '14 13:08 bquorning

similar experiences here. also on 10.9.4. Just experienced a kernel trap / grayscreen of death with gitx's name on it also (don't have further details on that tho, sorry)

jimabramson avatar Aug 12 '14 20:08 jimabramson

v0.15.1949 didn't introduce significant changes to the repository loading or refreshing; but avoiding excess work during the sort of workloads described has been a focus of that area in the preceding releases. Does disabling the repository watching in your GitX preferences alleviate the issue? Note that the window can still be manually refreshed with ⌘R

What version of git are you running (# which git; git --version)? GitX still leans heavily on parsing the output of the command line, and variations in the installed git version aren't covered by performance test sample repositories.

The kernel trap is very worrying; it's been a long time, and not in this project, but I have seen them related to FS event monitoring previously.

rowanj avatar Nov 10 '14 14:11 rowanj

I don't think the performance regression is fs related. I submitted #400 that fixes the regression.

ghost avatar Nov 11 '14 01:11 ghost