Opening our current project with git-disabled (via some registry hacks) takes about 7 minutes. Opening it with git-enabled takes over 2h, and the fans go full tilt for the whole duration. About 2 out of 5 times it crashes before getting into the project.
All this is well known, and documented; And has been ignored by the development team for years.
I just created a simple "Hello World". Opening time with git-plugin enabled ~1m35s. Opening time with git-plugin disabled ~15s.
(Each averaged over 10 tries.)
Paying any overhead for a feature that is not used/needed, and can not be disabled is just bad software design, or lazy programming, or both.
Why having the plugin enabled (aka not hacked out) is creating such a massive overhead is a riddle in itself. Even if it did full checksums for the full history of each file that shouldn't add up to more than 5-10% overhead - if very badly implemented.
(Yes, I am fully aware that the old "windows process creation spins on the main ui-lock" problem, but if that hits you ... just use a pool like everybody else.)
We have a local script that mentions https://developercommunity.visualstudio.com/solutions/587860/view.html as the source, but it looks like MS didn't like that, and deleted the info. Our script is internal, and does a lot of other things. Will try to extract the essence, and post it later.
11
u/andreasOM Apr 19 '21
Opening our current project with git-disabled (via some registry hacks) takes about 7 minutes.
Opening it with git-enabled takes over 2h, and the fans go full tilt for the whole duration.
About 2 out of 5 times it crashes before getting into the project.
All this is well known, and documented;
And has been ignored by the development team for years.