• 0 Posts
  • 16 Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle







  • It isn’t.

    On Linux, the OOM generally weighs 2 things, and based on those, starts killing processes until the system dies or goes back to life.

    The 2 things it weighs are memory footprint and how recent the process is.

    The reasoning is that, by killing a recently spawned process that is hogging a lot of memory, you will probably kill an unruly app that a user started and not a critical system component. Even in the case of servers with databases that use hundreds of GB of memory, it should in theory not kill them if there’s a recent process that has quickly hogged a lot of ram.

    Of course, it can still be a bit of a hit or miss (after all, it’s a last resource before crashing, and you can’t afford much complexity). But for the most part, it works well enough.

    Edit: I actually looked at the code. It doesn’t check if the process is recent. I don’t know where I read that it did. Maybe it was the OOM code for something else.

    There are still ways to mark an app as non oom killable, like a critical DB process. But it needs to be manually done.


  • I guess it may be smaller updates like .NET and some drivers. .NET and most of the other smaller updates shouldn’t even need restarting, they just eat your CPU and take ages because Microsoft is silently compiling them in the background on your computer.

    Nowadays, Microsoft Defender’s definitions are, for some reason, also shipped through Microsoft Update. You can get those daily or every few days, but they’re fast and won’t affect your system in any way.

    Drivers usually shouldn’t be common after installing the first batch, so I doubt you’d get a lot of those in 1.5 months.

    Indeed, Microsoft only ships system updates on patch tuesday, the second tuesday of the month.

    So this user could only have had a max of 2 system updates, 1-2 driver updates maybe (unlikely, though), and then possibly another 1-2 .NET updates. If the user has Defender activated, add a definitions update. Keep in mind that this is basically worst case scenario. Those updates should never cause issues, be that slow, or require 3 reboots.







  • Be careful with WD reds and CMR/SMR. Even though every WD Red Plus should be CMR, WD is known for selling SMR drives marketed as CMR. The whole Red Plus line exists because, before that, the WD Reds were supposed to be CMR, but they started mixing them with SMR drives. People found out and lawsuits were filed, so WD’s answer was to say that the WD Red line didn’t guarantee CMR, and people needed to pay extra for the WD Red Plus line.

    WD is forever off my list of trustworthy manufacturers. But there aren’t many options, and I understand that in these times it may be difficult to pass on a good offer. Read customer reviews and, upon arrival, make sure they’re CMR.