Comment

It also depends on what you mean by worse than Linux. A lot of the criteria that you’re evaluating definitely have Linux as better than Windows, but Windows is better than Linux in other ways that I notice on a day-to-day basis when I’m switching between the two.

Performance under memory pressure is the biggest one, I think. I don’t know why, but Windows handles extreme memory pressure and heavy page filing incredibly gracefully, whereas any Linux device I’ve used, and Macs, seems to stutter, slow down, and really struggle under memory pressure, even when there is superior hardware involved. I usually have to wait several minutes before my daily Linux driver recovers from heavy page filing, whereas it’s usually just a couple of seconds with my Windows box.

source

Sort:hotnew top

toddestan@lemmy.world ⁨1⁩ ⁨week⁩ ago
Windows has had to deal with memory pressure a lot more than Linux. Some of this is bloat, but historically there’s also just been a lot of low end systems sold with Windows. All of the Windows 7 systems sold with 1GB, the Windows XP systems sold with with 256MB, running Windows 98 in 16MB, and so on.

Windows is always looking for memory it can page out and does a lot of preemptive paging so that if it suddenly needs a bunch of free RAM - like if the user suddenly launches some memory hog of an application, Windows has it available. Windows is also a bit smart about it - it’ll page things out but still keep the data in RAM too. So for example an application idle in the background will be paged out in case Windows needs that memory, but it’s also kept in RAM so if the user pulls the application back up, Windows doesn’t have to read everything back from the page file either.

This has lead to complaints about Windows constantly thrashing the disk and doing things in the background, but there is some method to the madness. Though I will complain that Windows still seems to do this even in situations where the PC has a lot of RAM and large amounts of it aren’t being used.

The Linux kernel, on the other hand, doesn’t do a lot of this like Windows does. Which is fine so long as you have enough RAM. But in a situation where there isn’t a lot of free RAM and suddenly the user launches a big application, the kernel suddenly has to do a bunch of swapping to free up memory and that can take a bit, especially if the drive is slow.

The Linux kernel does have a “Swappiness” setting that can modify its behavior, but I’ve never really played around with that myself.

source
- douglasg14b@lemmy.world ⁨1⁩ ⁨week⁩ ago
  Thank you for thoughtfully engaging. I appreciate your knowledge.
  
  source
ProdigalFrog@slrpnk.net ⁨1⁩ ⁨week⁩ ago
That behavior with Linux is absolutely real, and it’s very weird that it hasn’t been fixed in over a decade. It’s due to the default OOM (out of memory) killer being way too conservative with killing an application when the memory is completely full and disk swapping. Some people have solved this with an app that watches for OOM situations and acts with more decisiveness to kill an offending application before it swaps and brings the system to a halt, called EarlyOOM.

That still isn’t quite as good as Windows handling though, as Windows can generally handle those situations without killing the application at all.

source
- douglasg14b@lemmy.world ⁨1⁩ ⁨week⁩ ago
  TIL!
  
  Awkwardly, I find that the largest memory pressure tends to come from a particular web page that continually gobbles up more memory the longer it is open.
  
  There’s always one of these somewhere, and I’m bad at closing tabs. I usually notice pretty quickly when I come back to my computer. As soon as we start hitting page filing, since everything is stuttering and slow, but if it goes overnight, it can literally be 15 to 20 minutes before the system is responsive again after I kill the offending process.
  
  Whereas on my work device, which is Windows, I usually might not even notice until I’ve maxed out my page file, which can be 64 or 128 GB depending on the device. And even then, I only notice because file operations start getting slow because the SSD is being thrashed. Killing the offending process results in responsiveness usually within a few seconds and a full clear out of the page file in a couple minutes.
  
  The explanations that I’ve gotten from another commenter make a lot of sense. That Windows has just always had to deal with high memory pressures, so has been forced to mature in that sense. It is rather odd that Linux is behind on this, though, given its overwhelming representation in headless environments
  
  source
thanatotus@lemmy.ml ⁨1⁩ ⁨week⁩ ago
I dont know; this seems like super specific case where you’ve economic means to afford or be around all of those high end systems and the same hardware is underpowered for your use case.

My first personal laptop had Windows 7 but as soon as Windows 8 came it struggled (only having measly 2GB of RAM) - so i switched to Ubuntu and it was a breeze for the next 10 years. I always used to try new version of Windows when released but it they always seemed to be memory hog and become bloated over time.

source
- aim_at_me@lemmy.nz ⁨1⁩ ⁨week⁩ ago
  You kind of haven’t addressed the point though, you’ve just pointed out that linux experiences memory pressure less often.
  
  But OPs point is that Windows is better at it when you inevitably fill its memory. I run multiple clusters of docker containers and virtualised systems in my day to day, and its true that linux (Ubuntu at least) isn’t the best at huge memory pressure, especially when I fill swap. And I’m running the latest intel chip with 32gb. I wish I’d gone 64gb… but, memory prices.
  
  source
  - thanatotus@lemmy.ml ⁨1⁩ ⁨week⁩ ago
    My response wasn’t about memory pressure but rather how that scenario is rather specific.
    
    I havent used windows for years so i don’t know if it performs better or worse than say Ubuntu or Fedora under memory pressure.
    
    source