We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was not able to find an open or closed issue matching what I'm seeing, including in the git-for-windows/git tracker.
git-for-windows/git
Issue #3840
microsoft/git
64-bit
$ git --version --build-options TestCase1: git version 2.35.3.vfs.0.0 cpu: x86_64 built from commit: d34442f3ab072056eab72131c02abcf76b32d827 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon TestCase2: git version 2.43.0.vfs.0.0 cpu: x86_64 built from commit: b7a6ed788a205fb2c0013111d277b4c9d6ab35bd sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon
Are you using Scalar or VFS for Git?
Scalar
$ cmd.exe /c ver Microsoft Windows [Version 10.0.19045.3803]
Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
CMD
What commands did you run to trigger this issue? If you can provide a Minimal, Complete, and Verifiable example this will help us understand the issue.
git pull
What did you expect to occur after running these commands?
The completion time of running "git pull" with git version 2.43.0.vfs.0.0 can be close to git version 2.35.3.vfs.0.0.
What actually happened instead?
Since git version 2.36, the execution time of "git pull" has become significantly longer. I tried using the following commands to log the details:
set GIT_TRACE2_PERF=1 set GIT_TRACE_PACK_ACCESS=1 set GIT_CURL_VERBOSE=1 git pull
Git-2.35.3.vfs.0.0-64-bit:
Git-2.43.0.vfs.0.0-64-bit:
The local repositories used for testing are generated by executing "scalar clone" after installing the corresponding git version.
If the problem was occurring with a specific repository, can you specify the repository?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I was not able to find an open
or closed issue matching
what I'm seeing, including in the
git-for-windows/git
tracker.Issue #3840
Setup
microsoft/git
are you using? Is it 32-bit or 64-bit?64-bit
Are you using Scalar or VFS for Git?
to the issue you're seeing?
Details
Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
What did you expect to occur after running these commands?
The completion time of running "git pull" with git version 2.43.0.vfs.0.0 can be close to git version 2.35.3.vfs.0.0.
What actually happened instead?
Since git version 2.36, the execution time of "git pull" has become significantly longer. I tried using the following commands to log the details:
Git-2.35.3.vfs.0.0-64-bit:
Git-2.43.0.vfs.0.0-64-bit:
The local repositories used for testing are generated by executing "scalar clone" after installing the corresponding git version.
If the problem was occurring with a specific repository, can you specify
the repository?
The text was updated successfully, but these errors were encountered: