Closed angelodiego closed 3 years ago
Shell scripts do run slow in Git for Windows. Part of it is that many processes are spawned (for which Windows is not optimized, it is much more optimized for running multi-threaded software), part is that antimalware usually adds insult to injury. You might be able to accelerate git flow
by adding an exception to Defender et al so that they do not scan bash.exe
all the time.
Shell scripts do run slow in Git for Windows. Part of it is that many processes are spawned (for which Windows is not optimized, it is much more optimized for running multi-threaded software), part is that antimalware usually adds insult to injury. You might be able to accelerate
git flow
by adding an exception to Defender et al so that they do not scanbash.exe
all the time.
Unfortunately Bash is already ignored by f-sercure (windows defender is not active). I understant that bash is slow but it looks suspicious that the setup part takes such an insane amount of time, there is virtually no disc access or anything like it that could justify such a slow process, am I the only one experiencing this kind of problems with git flow?
Closing stale ticket.
Setup
$ cmd.exe /c ver
Microsoft Windows [version 10.0.18362.592] (c) 2019 Microsoft Corporation. Tous droits r▒serv▒s.
git flow to run almost immediately, there is no difference between the develop and master branch
it took more than 20 seconds to finish
any repo will show the problem
It looks like that the setup takes almost 20 secs and a couple of seconds are actually spent doing the branch merges (starting from git checkout master)