Gitup: very slow map view for large repositories

[jeroenvollenbrock]

I noticed that the responsiveness of GitUp becomes terrible when i use it on a large repo, for instance when i want to prepare a set of patches to the linux kernel. (This often involves some splitting and swapping). I think this is due to the re-rendering of the entire tree upon each change, while i'm only interested in the very top of it. Would it perhaps be possible to limit this view to show only commits up to a specific point in the history in order to increase the speed into usable levels?

[swisspol]

Do you mean the Map View?

[jeroenvollenbrock]

Yes, i mean the map view, excuse me for the ambiguity.

[swisspol]

Did you try hiding as many branches as possible?

[jeroenvollenbrock]

Yes, I've disabled all view options, but it remains slow. Even toggling just the "virtual branch tips" option takes two minutes to re-render the view.

[jeroenvollenbrock]

I also had only two local branches checked out, so i don't think that was causing any problems either

[jeroenvollenbrock]

It's actually quite easy to reproduce the problem, disable all view options, check out just the master branch of https://github.com/torvalds/linux, and try to swap the two topmost commits

[lilyball]

I really hope the new tag means someone is going to look at this issue. This performance problem is why I've largely stopped using GitUp, even though the repo I'm working on isn't nearly as large as the Linux repo.

[lucasderraugh]

Unfortunately these performance issues are not something we’ve addressed. I understand the frustration though and perhaps I’ll try to focus on some of these perf issues for the next release.

[richardtop]

Hiding remote branches solved the issue for me. Performance is still not stellar, but way better than if showing all of the branches.