3 ms·
Are you talking about WSL1 or WSL? Wsl2 is much much faster due to having a virtualized real linux kernel running
by hasperdi 5y ago
Are you talking about WSL1 or WSL? Wsl2 is much much faster due to having a virtualized real linux kernel running
- scandinavian 5y agoAccessing the WSL filesystem from WSL is indeed a lot faster on WSL2. Accessing the Windows filesystem from WSL or vise versa is even slower in WSL2 compared to WSL1. https://docs.microsoft.com/en-us/windows/wsl/compare-versions#comparing-features https://docs.microsoft.com/en-us/windows/wsl/compare-version... > As you can tell from the comparison table above, the WSL 2 architecture outperforms WSL 1 in several ways, with the exception of performance across OS file systems.
- easton 5y agoSystem performance is, IO between Windows and Linux isn’t. https://github.com/microsoft/WSL/issues/4197 https://github.com/microsoft/WSL/issues/4197
- speed_spread 5y agoWSL2 disk access from the Windows side is very slow. It's the reciprocal problem of WSL1. WSL2 Linux apps now get proper performance now but if your IDE is on the Windows side, access time to project files on native Linux partition is terrible.
- LaGrange 5y ago...actually e.g. VS Code has a really great split backend, so you can actually have the frontend "properly" on Windows anyway, and yet still use WSL2. My own case was something different: annoyingly configured automated browser tests with Cypress. Just running them inside WSL and letting that start a browser on the distro itself was the most comfortable way to debug these.