You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your link "WSL1 Installation Guide - Microsoft's official guide for WSL." now points to WSL2 instructions.
It's worth keeping in mind that not everyone can access the store (e.g. All "Windows N" people do not have the store, or any of the other telemetry/bloat), so they have no other option but stuff like this:-
Also, you say WSL2 has faster file-system-access... are you sure??? In my tests, WSL2 was 10 to 100 times slower than WSL1 when accessing my files. It kinda makes sense too - WSL1 natively translates the filesystem calls, but WSL2 has to go through the entire virtualization boundary to do the same thing.
It annoyed me sufficiently that I switched back to from WSL2 to WSL1 in fact (FYI - I've got two SN850X NVMe's in raid0, so slowness of the OS is extremely obvious on my setup)
The text was updated successfully, but these errors were encountered:
Your link "WSL1 Installation Guide - Microsoft's official guide for WSL." now points to WSL2 instructions.
It's worth keeping in mind that not everyone can access the store (e.g. All "Windows N" people do not have the store, or any of the other telemetry/bloat), so they have no other option but stuff like this:-
Also, you say WSL2 has faster file-system-access... are you sure??? In my tests, WSL2 was 10 to 100 times slower than WSL1 when accessing my files. It kinda makes sense too - WSL1 natively translates the filesystem calls, but WSL2 has to go through the entire virtualization boundary to do the same thing.
It annoyed me sufficiently that I switched back to from WSL2 to WSL1 in fact (FYI - I've got two SN850X NVMe's in raid0, so slowness of the OS is extremely obvious on my setup)
The text was updated successfully, but these errors were encountered: