-
Notifications
You must be signed in to change notification settings - Fork 204
Very slow to refresh with latest update (0.15.1949) #373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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. |
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. |
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) |
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 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. |
I don't think the performance regression is fs related. I submitted #400 that fixes the regression. |
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.
The text was updated successfully, but these errors were encountered: