3 ms·
That has been my experience as well. WSL2 is much much faster.
by tilolebo 6y ago
That has been my experience as well.
WSL2 is much much faster.
- mehrdadn 6y agoDo you specifically mean \\wsl$ is much faster on WSL2?
- tilolebo 6y agoAny interaction with the linux filesystem. With WSL 1 installing an Ubuntu package or performing an upgrade was unbearably slow, with WSL 2 it feels normal. \\wsl$ is also much faster, yes
- mehrdadn 6y agoNormal interactions from within WSL of course feel normal. It's just a VM with a fancy name after all. Which is removing pretty much all the overhead of the Windows I/O system, and which has hence been faster for ages. I'm surprised \\wsl$ would be faster though; that should have more overhead going through a VM, not less. If I ever try out WSL2 I'll have to give it a shot, but somehow my past experiences don't leave me optimistic...
- tilolebo 6y agotime grep -ri asfadsfadfg /home/me/python-venvs 0.79s user 0.14s system 99% cpu 0.928 total wsl time grep -ri asfadsfadfg /home/me/python-venvs 0.83s user 0.10s system 99% cpu 0.932 total EDIT: cleaned up and formatted the output for better visibility, reacting to your comment. First command ran from a zsh Terminal session in WSL Second one ran from a powershell session using the wsl "bridge" executable.
- mehrdadn 6y agoI can't make sense of your command lines (why are you passing grep to grep??), but you're comparing pure-Windows against pure-WSL? I was comparing the two of those against \\wsl$ which is the slow one...