-
Notifications
You must be signed in to change notification settings - Fork 823
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
Poor performance with WSL2 and Windows 11 #11565
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
WslNetworkingLogs-2024-05-07_10-23-15.zip Here the WSL logs |
Diagnostic information
|
View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
Diagnostic information
|
View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
Diagnostic information
|
View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
Diagnostic information
|
Thank you @matpil. This delay could be caused by a variety of things, like a slow network connection, or a slow authentication go git. Do you see the same behavior if let's say you clone / pull a public repo, like https://github.com/microsoft/WSL ? |
Thank you for confirming @matpil. The fact that cloning a public repository doesn't reproduce the issue shows the performance problem doesn't come from WSL, so I'll close this issue. Here are a couple ideas to help you root cause the issue:
|
Windows Version
Microsoft Windows [Versione 10.0.22631.3447]
WSL Version
2.2.3.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04
Other Software
git version 2.39.2
Debian version 12.5
Repro Steps
fresh Debian installation
cloning repo git on native wsl2 fs
launch a "git pull" command
Expected Behavior
The "git pull" execution time should be around 3-4 seconds
Actual Behavior
The “git pull” execution time takes up to 20-22 seconds
Diagnostic Logs
WslNetworkingLogs-2024-05-07_10-23-15.zip
The text was updated successfully, but these errors were encountered: