3 ms·
> WSL doesn't run the full slew of linux processes and uses the same memory space, so both CPU and memory utilisation is much lower than a VM. Well, I thought
by TheRealDunkirk 5y ago
> WSL doesn't run the full slew of linux processes and uses the same memory space, so both CPU and memory utilisation is much lower than a VM.
Well, I thought this was the case with WSL, but that WSL2 changed this, such that it's really just a full-blown VM now. Are you saying that you're still using WSL 1, or have I misunderstood the nature of WSL2?
- jve 5y agoWSL2 still runs instantly. I haven't been bothered with waiting. I tried wsl --shutdown and then opening wsl - didn't take a second. Cold boot may have been longer, but I don't remember being bothered with startup times. However older powershell console startup time did bother me for sure.
- alxlaz 5y agoNeither :-). WSL2 runs a full-blown machine but the startup process is considerably different from that of a real machine with a real Linux installation, so when you "start up" a WSL2 shell, it's spawned in seconds, you're already logged in and so on. It's essentially the WSL1 presentation format but with a different back-end.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- girvo 5y agoThough my Ubuntu VM on Hyper-V with multipass giving the Microsoft Terminal integration started up basically just as fast, to be honest. But the deeper integration and lighter underlying OS for WSL2 is better, especially for Docker dev container usage with VSCode.