2 ms·
My experience with WSl2 is not great so far. There seems to be some memory management process in Windows that starts eating enormous amounts of cpu cycles for l
by PeterStuer 2y ago
My experience with WSl2 is not great so far. There seems to be some memory management process in Windows that starts eating enormous amounts of cpu cycles for long periods at inconvenient times. This does not happen when I run the same setup in a same distro on the same hardware and Windows installation under Hyper-V.
- andai 2y agoIs this process part of Windows or WSL? In my experience Windows itself (without WSL) loves eating my CPU at its earliest convenience, even waking up my (unplugged) laptop from sleep for a chance to do so... (see recent HN thread)
- PeterStuer 2y agoIt is a windows process. As for the waking up, there is a setting somewhere in power options that you can set to disallow programs to schedule machine starts (even when the PC is fully shut down). Sadly, Windows ships with allow wakeups by default.