Very Slow prompt return

[developingchris]

It takes several seconds for the branch and change stuff to show up.
Is this a core thing in posh-git.

I'd love to understand more about the implementation of how the information is gathered from the repo.

[developingchris]

This is repeatable on several normally sized repos. I believe it comes down to all of the test-paths inside the get Git branch. call. But are they all necessary. doesn't the "git branch" command provide you with sufficient info to determine the branch?

[dahlbyk]

Performance has been an open issue pretty much from the beginning. You can set $GitPromptSettings.Debug = $true to get a better idea where your performance bottleneck is.

The most common msysgit configuration uses git.cmd, which adds environment overhead to every call. To speed things up a bit you can use git.exe instead of git.cmd. You just have to port some of the settings in git.cmd into your PowerShell profile. Something like this:

$GitInstallDir = 'C:\Program Files (x86)\Git'
$Env:Path = "$GitInstallDir\bin;$GitInstallDir\mingw\bin;$Env:Path"
if(!$Env:HOME) { $Env:HOME = "$Env:HOMEDRIVE$Env:HOMEPATH" }
if(!$Env:HOME) { $Env:HOME = $Env:USERPROFILE }

$Env:PLINK_PROTOCOL = 'ssh'

On my system that trimmed around 300ms off every git call.

Beyond that, by default posh-git should populate almost everything in the prompt from parsing a single git status call and checking for the existence of a few files. If git status is slow, posh-git will be slow.

You can also set $GitPromptSettings.EnableFileStatus = $false to skip the git status call altogether - parsing branch information manually is much faster.

[rkeithhill]

Maybe we should close this issue given its age and the fact that I'm seeing prompt times in the area of <100 ms on small repos and ~300 ms on medium size repos (6500 files).

[dahlbyk]

Between improvements in Git for Windows, #208, and various posh-git optimizations, I think we're doing about as well as we can.