2 ms·
So this sound like the CPU usage will be quite a bit higher than with wsl1, since it's actually running a VM. Kind of like Docker on Mac. It's not a huge issue,
by viraptor 8y ago
So this sound like the CPU usage will be quite a bit higher than with wsl1, since it's actually running a VM. Kind of like Docker on Mac. It's not a huge issue, but it still takes some battery life away.
- cpuguy83 8y agoVM does not mean extra CPU usage. Since there is no emulation involved (assuming VT-x is supported) you should be getting native or mostly native performance.... not to say that WSL2 will be better on CPU usage, however I don't think one should assume that it will be worse. This is opposed to WSL1 which is emulation and has extra layers to go through.
- viraptor 8y agoUnless they completely stripped all background tasks, there's still a few wakeup calls from the VM. I didn't mean the execution overhead from emulation. For example hyperkit.docker not running any container does ~90 wakeups/s on my machine. This comes mainly from just keeping the VM alive. This also prevents deeper sleep for CPUs.