4 ms·

I'm a SourceTree user on Mac. Just tried GitUp out for an hour. Here are the problems I have with SourceTree: * Slow as hell * No/bad keyboard shorts, and se

by dcre 11y ago

I'm a SourceTree user on Mac. Just tried GitUp out for an hour. Here are the problems I have with SourceTree: * Slow as hell * No/bad keyboard shorts, and setting up custom ones is annoying and buggy * Uses tons of memory — it eventually gets up to 1 GB after running for a day or two, and my repos are not very big. My thoughts on GitUp: * Crazy fast (almost disarmingly so – I think it needs more visual confirmation when things happen) * Excellent commit/staging view. Reminds me of GitExtensions, a nice Git GUI for Windows * I love the focus on keyboard shortcuts. They work really well in the commit view * Map view is truly awful. I get that it's a work in progress, but I have no idea what its organizing principle is. Too much pointless whitespace. It radically overprivileges old branches and commits. I don't see a way to focus on what I did most recently. * The list of commits (Cmd+D) in the map view is useless

kohanz 11y ago
> Here are the problems I have with SourceTree: > * Slow as hell Good to know I'm not the only one with this issue.
- joshschreuder 11y ago
  There have been serious issues with performance in the 1.6 releases (including Windows). There are a few Git specific things if you're running Git < v2 that you can try: https://stackoverflow.com/questions/4485059/git-bash-is-extremely-slow-in-windows-7-x64/24045966#24045966 https://stackoverflow.com/questions/4485059/git-bash-is-extr... And in Sourcetree, set options under Options -> Diff, set Size Limit (Text) to 128KB and Size Limit (Binary) to 1024KB.
swisspol 11y ago
Thanks for trying GitUp and for the feedback! > The list of commits (Cmd+D) in the map view is useless Could you provide feedback on http://forums.gitup.co http://forums.gitup.co about what you are specifically trying to do or what your workflow is?
- dcre 11y ago
  Sure.
Danack 11y ago
The slowness appears to be caused by continual directory scanning. For me at least, turning off the "Refresh when files change" option, and so having to do "view, refresh" or Command-R, made SourceTree be zippy again. And as I'm usually on a laptop, having less continued CPU usage is a good tradeoff against having to press refresh when I'm going to do something in SourceTree.
- dcre 11y ago
  Good point. I have auto-refresh off and it helps a lot, but I still find the UI feels laggy.
- Too 11y ago
  Does not work, i've also heard from other sources that turning this option on makes it faster because then it uses some native file-changed-hooks instead of continuously polling the directory. For me both options are equally slow and many forum posts say the same. Sourcetree performance simply is crap and no fiddling with the options fixes this, nor should this fiddling be required. You can find bug tickets about performance issues dating back years but nothing happens, don't waste your time on sourcetree just because it looks shiny, use a tool that actually works.
rurban 11y ago
Confirmed. But Cmd+D in the map view is excellent, not useless. Compressing the mapview (less white space) or zooming (Ctrl-+/Ctrl--) would be nice. I never tried SourceTree, but used to work with macports gitk, which started missing redraws lately. There is no comparison. GitUp is excellent.
minnsey 11y ago
Hi, Sorry to hear about your issues with SourceTree, but thanks for highlighting them. We are aware of performance issues for a number of users. To be fair it is taking us longer than we would like but, addressing these issues is our priority and we're working on it. If you haven't already consider raising an issue, at https://jira.atlassian.com/browse/SRCTREE https://jira.atlassian.com/browse/SRCTREE for OSX or https://jira.atlassian.com/browse/SRCTREEWIN https://jira.atlassian.com/browse/SRCTREEWIN for Windows, with info about your environment. Thanks

by dcre 11y ago

kohanz 11y ago

> Here are the problems I have with SourceTree: > * Slow as hell Good to know I'm not the only one with this issue.

joshschreuder 11y ago
There have been serious issues with performance in the 1.6 releases (including Windows). There are a few Git specific things if you're running Git < v2 that you can try: https://stackoverflow.com/questions/4485059/git-bash-is-extremely-slow-in-windows-7-x64/24045966#24045966 https://stackoverflow.com/questions/4485059/git-bash-is-extr... And in Sourcetree, set options under Options -> Diff, set Size Limit (Text) to 128KB and Size Limit (Binary) to 1024KB.

swisspol 11y ago

Thanks for trying GitUp and for the feedback! > The list of commits (Cmd+D) in the map view is useless Could you provide feedback on http://forums.gitup.co http://forums.gitup.co about what you are specifically trying to do or what your workflow is?

dcre 11y ago
Sure.

Danack 11y ago

The slowness appears to be caused by continual directory scanning. For me at least, turning off the "Refresh when files change" option, and so having to do "view, refresh" or Command-R, made SourceTree be zippy again. And as I'm usually on a laptop, having less continued CPU usage is a good tradeoff against having to press refresh when I'm going to do something in SourceTree.

dcre 11y ago
Good point. I have auto-refresh off and it helps a lot, but I still find the UI feels laggy.
Too 11y ago
Does not work, i've also heard from other sources that turning this option on makes it faster because then it uses some native file-changed-hooks instead of continuously polling the directory. For me both options are equally slow and many forum posts say the same. Sourcetree performance simply is crap and no fiddling with the options fixes this, nor should this fiddling be required. You can find bug tickets about performance issues dating back years but nothing happens, don't waste your time on sourcetree just because it looks shiny, use a tool that actually works.

rurban 11y ago

Confirmed. But Cmd+D in the map view is excellent, not useless. Compressing the mapview (less white space) or zooming (Ctrl-+/Ctrl--) would be nice. I never tried SourceTree, but used to work with macports gitk, which started missing redraws lately. There is no comparison. GitUp is excellent.

minnsey 11y ago

Hi, Sorry to hear about your issues with SourceTree, but thanks for highlighting them. We are aware of performance issues for a number of users. To be fair it is taking us longer than we would like but, addressing these issues is our priority and we're working on it. If you haven't already consider raising an issue, at https://jira.atlassian.com/browse/SRCTREE https://jira.atlassian.com/browse/SRCTREE for OSX or https://jira.atlassian.com/browse/SRCTREEWIN https://jira.atlassian.com/browse/SRCTREEWIN for Windows, with info about your environment. Thanks