this post was submitted on 26 Nov 2024
454 points (97.7% liked)

196

16588 readers
1929 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
moss@lemmy.blahaj.zone
greembow@lemmy.blahaj.zone
moss@lemmy.world
queue@beehaw.org
funky_rodent@lemmy.blahaj.zone
PeachyMcPeachface@lemmy.blahaj.zone
threegnomes@lemmy.blahaj.zone
greembow@lemmy.world
remotelove@lemmy.ca
Roflmasterbigpimp@feddit.de
qaz@lemmy.world
A_Very_Big_Fan@lemm.ee
qaz@lemmy.blahaj.zone
qaz@lemmy.ca
A_Very_Big_Fan@lemmy.world
qaz@lemmy.dbzer0.com
Qaz@lemmy.ml
qaz@sh.itjust.works
qaz@lemmy.sdf.org
454
firefox rule (slrpnk.net)
submitted 15 hours ago by blibla@slrpnk.net to c/196@lemmy.blahaj.zone
68 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Badabinski@kbin.earth 6 points 14 hours ago (1 children)

The issue is that browsers don't release much memory back to the system when it's needed. I wish they'd work more like the Linux kernel's VFS caching later, but they don't (and might not be able to. For example, I do don't think the Linux kernel has good APIs for such a use case).

[โ€“] zea_64@lemmy.blahaj.zone 3 points 9 hours ago

You can write limits to and then poll files in /proc/pressure/ to be notified of resource pressure. Systemd will also set an environment variable for similar files for your cgroup.