1058

Some system load graphs of last 24h (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by ruud@lemmy.world to c/lemmyworld@lemmy.world

191 comments fedilink hide all child comments

For those who find it interesting, enjoy!

you are viewing a single comment's thread
view the rest of the comments

[-] FrostyCaveman@lemm.ee 27 points 1 year ago

Damn that’s a huge chunk of (what looks like) a 64 core CPU there. Impressive!

It’s cool it can aggressively cache that much. Although I am perplexed why one would have a swap file configured in this case? What does it give you here? Sorry not trying to be an elitist or anything just have no idea what advantage you get!

[-] ruud@lemmy.world 20 points 1 year ago

To be honest I tend to use swap less and less. But this was in the build that Hetzner does and I didn't remove it.

[-] DoomBot5@lemmy.world 13 points 1 year ago

If your application goes wild with RAM usage, a properly configured swap will make sure the underlying OS remains responsive enough to deal with it.

[-] steventhedev@lemmy.world 4 points 1 year ago

The OOM killer is usually triggered after it starts hitting the disk. Which means your system is unresponsive for a long time until it finally kills something.

Using something like oomd can help trigger before it hits swap but then why are you using swap in the first place?

The bigger issue is that the kernel sometimes ignores the swappiness and will evict code/data pages long before file cache even when set to 0 or 1. I'm still not sure if that was because of an Ubuntu patch or if it was an issue that's been resolved in the years since I last saw this