this post was submitted on 05 Jul 2023
1719 points (99.1% liked)

Lemmy.World Announcements

29095 readers
301 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations ๐Ÿ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

For those who find it interesting, enjoy!

you are viewing a single comment's thread
view the rest of the comments
[โ€“] JATtho@lemmy.world 1 points 1 year ago (1 children)

Welp, my only calculation was "64 cpu threads * 30% load -> ~19 cores busy", I may be guilty of rounding up too much... The RAM usage is intresting however, since the kernel seems to be caching all it can, to point ejecting uneeded data into swap in order to retain the disk cache. If more ram is reserved by running processes, the (likely pict-rs, database services) disk access times will begin to degrade.

[โ€“] Molecular0079@lemmy.world 1 points 1 year ago

It could also be all 64 threads being used lightly with the scheduler trying to spread the load out evenly.

Not sure what the exact situation regarding swap in that graph, but I've also had the kernel preemptively use swap for rarely used chunks of memory in favor of cache when running long-running processes. Its probably relatively normal.