Skip to content
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

git pull takes a long time #621

Open
1 of 6 tasks
v-liuweining opened this issue Jan 2, 2024 · 0 comments
Open
1 of 6 tasks

git pull takes a long time #621

v-liuweining opened this issue Jan 2, 2024 · 0 comments

Comments

@v-liuweining
Copy link

v-liuweining commented Jan 2, 2024

Setup

  • Which version of microsoft/git are you using? Is it 32-bit or 64-bit?

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
  • Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver

Microsoft Windows [Version 10.0.19045.3803]
  • Any other interesting things about your environment that might be related
    to the issue you're seeing?

Details

  • 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?

    • Public repo: insert URL here
    • Windows monorepo
    • Office monorepo
    • Other Microsoft-internal repo: GendoxData
    • Other internal repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant