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 push is super slow even inside WSL file system #9233

Closed
1 of 2 tasks
Ruminateer opened this issue Nov 30, 2022 · 1 comment
Closed
1 of 2 tasks

Git push is super slow even inside WSL file system #9233

Ruminateer opened this issue Nov 30, 2022 · 1 comment

Comments

@Ruminateer
Copy link

Ruminateer commented Nov 30, 2022

Version

Microsoft Windows [Version 10.0.22621.819]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.15.74.2-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04.1 LTS

Other Software

Inside WSL

$ git --version
git version 2.34.1

On the Windows side (for contrast)

> git --version
git version 2.38.1.windows.1

Repro Steps

  1. Create a large git repo inside WSL $HOME
  2. Push the repo to a newly created GitHub repo using the git inside WSL
  3. For contrast, copy/move the folder into the windows file system
  4. Push the repo to a newly created GitHub repo using git for Windows

Expected Behavior

Git inside WSL has a similar push speed as git for Windows.

Actual Behavior

With git for windows, the speed of Writing objects is around 1.3MiB/s.

> git push -u origin master -f
Enumerating objects: 3132, done.
Counting objects: 100% (3132/3132), done.
Delta compression using up to 12 threads
Compressing objects: 100% (914/914), done.
Writing objects: 100% (3132/3132), 235.07 MiB | 1.30 MiB/s, done.
Total 3132 (delta 2207), reused 3132 (delta 2207), pack-reused 0
remote: Resolving deltas: 100% (2207/2207), done.
To https://github.com/Ruminateer/Match-and-Shoot.git
 + 000075d...218af5a master -> master (forced update)
branch 'master' set up to track 'origin/master'.

However, with git inside WSL, the speed of Writing objects is only around 25KiB/s under the same network, and sometimes completely stuck.

Diagnostic Logs

No response

Copy link
Contributor

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

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