Improve performance for very large commits
If I select a commit with a very large number of moved/modified files, (e.g. >10k), GitKraken hangs completely for several minutes. This is especially annoying if such a commit is the latest commit since GitKraken will hang immediately upon startup. Same thing happens when rebasing and such commits are involved.
Perhaps GitKraken could skip generating the changes list if the number of changes is very large (I guess no one would manually look through that many changes anyway).
Comments: 2
-
10 Feb, '22
Lucien Murray-PittsI also have this problem, I had it before but we didnt realize this was the problem and just gave up using Kraken.
Again we are working on a new repo with 4GB, 1-200K files, but only 10 commits (freshly checked in old project code) and its very very sluggish.
Machine is a 40+ core Xeon Gold server with 3TB RAM, and 2TB SSD raid for the repo, so its not an issue of machine performance itself. -
16 Apr, '22
Sandra CapriAnytime I have a commit (or am ready to commit) several thousand files, GitKraken takes > 100% of my CPU, and becomes unusable (several minutes to update the file window). I have to kill it and use the git command line only - in a terminal window - I can't use any part of GitKraken.. The git command line might take 10 or so seconds to output the results of a "git status" - but doesn't bring my system to its knees like Gitkraken will. I can do a git diff on the command line, and though there might be a couple of second pause, it's still usable.
It would be nice if after a few hundred files were discovered to be changed between 2 commits or as changes to the working directory, that you would stop processing those and just output as much as needed to fill the file window.
This has been a GitKraken problem for a long time. I only notice it when we update our version of the SDK which is generally a new directory of 8-11K files.
Platform: darwin (x64)
Version: 8.3.3