| ▲ | skydhash 3 hours ago | |||||||
The thing with windows is that there is no idle state, something is always busy with the CPU/hogging ram. With Linux I can have like 98% idle and the system taking 2Gb out of my 8gb of ram, but with windows, the system is more like 30% cpu and more than 4GB of currently being used ram. | ||||||||
| ▲ | PorciiVorbesc 3 hours ago | parent | next [-] | |||||||
If idle on Win 11 already pre-caches most-used apps like Chrome/FF and not on Linux, how can you accurately measure what true idle is? You have to remember the Win (and MacOS) kernel is tuned to consumer desktop user use cases, while Linux kernel is tuned to server/DC use-cases. That's why ~15 years ago when I was in uni, you'd get audio stutter when playing music/movies of spinning rust on linux while torrenting file on the same HDD, and not on Windows/MacOS, due to different queuing algorithms used thet prioritised audio decoding tasks over everything else, which Linux kernel out of the box didn't, unless you tinkered and changed it. | ||||||||
| ||||||||
| ▲ | keyringlight 2 hours ago | parent | prev [-] | |||||||
A tangent to this which annoys me is not specifically windows, but the way the ecosystem has evolved over the years, by guidance/enforcement or lack thereof from MS. Unless you're very careful about what applications you install and how you manage/monitor them, you can end up with a lot of background applications loaded each boot, each doing some combination of non-centralized updating itself or applications it manages, preloading, quick launch, etc. | ||||||||