-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very slow git credential manager #424
Comments
From the logs I can see there is about a 1.6 second startup time, which is largely unavoidable. There may be some perf wins we can make from some optimisations or better use of AOT compilation (with a move to .NET 5/6 on Windows).
However the largest bulk of time spent in GCM is doing the remote probing network call, for auto-detection of host providers; at least 2.8 seconds.
Since it looks like you're using a "generic" provider here for the Run the following to set Git configuration, telling GCM to use the "generic" provider (it won't make this probe call) for the host: git config --global credential.https://XXXXX.provider generic ..where |
The suggestion to set the provider to generic reduced the total clone time from 20 seconds down to around 5 seconds which is a huge improvement. It is still much slower on this specific machine so I am going to work with my IT team to figure out if a security agent is making normal operations slower. |
@vtbassmatt to document |
Is there a reason the GCM is called twice to 'store'? See logs in OP. |
@vtbassmatt not sure if this is still worth documenting as the latest GCM release will automatically set this setting for you after 1 successful auto-discovery probe? |
Whoops, sorry for the lack of followup here. I'll still try to mention it someplace, but good to know it'll be encountered less frequently now! |
Which version of GCM Core are you using?
2.0.498+7ad55fb809
Which Git host provider are you trying to connect to?
Local gitea instance
Can you access the remote repository directly in the browser using the remote URL?
Expected behavior
When I do a Git clone of a repository, I expect the clone operation to happen quickly but each invocation of the git credential manager takes at least 5 seconds. See the logs below. The operations complete without prompting me for my password but they are just very slow.
Actual behavior
The operation occurs successfully.
Logs
Performance Logs
Git/GCM Trace Logs
The text was updated successfully, but these errors were encountered: