I have particularly nasty repo: 114 thousand files in a single (initial) commit. The size of the “.git” folder ~1GB. Same ballpark for the working folder on an SSD disk.
Whenever I click on this initial commit, it takes 10-13 seconds to populate the UI with all the files/changes. The UI is stuck during this time, without any indicator.
Nevertheless, this is quite an achievement. SourceTree (my current GIT client) does it in approximately 50 seconds. And its UI is frozen too. Memory usage is the same (approx 1GB).
I have noticed, that while scanning, sublime-merge utilizes a single CPU core to 100%, but the rest of the cores are idle. Would it be theoretically possible to use multiple cores (even though I know when UI is involved, usually it needs to be done on the main thread) for scanning / processing the GIT commit?