@sxa the new zram stuff doesn't help (but probably better than trashing SSD cell write limits)
@ben Hmm I hadn't spotted that zram is already running on here (Fedora 43) and seems to be accounting for all of the 8GiB of swap 🤔
@sxa yeah, that's the default now. I added an extra 2gb swap file to mine as I kept running out and the OOM would kill vscode
@ben Just gave it shot using the commands in https://www.guyrutenberg.com/2024/12/14/setting-up-a-swap-file-on-btrfs/ - will see how it works out :-)
Thanks for the hints
@ben Unfortunately after adding 8GiB swap on my machine it still seems that it just chews through it all and the behaviour isn't any different from before. The same things seem to cause my OOM conditions. Grrr
Apparently adding swap to zram doesn't work well.
I found this which explained a lot (and explains why Fedora went with zram to prevent memory ever getting written to disk)
Removing the zram might be better
https://chrisdown.name/2026/03/24/zswap-vs-zram-when-to-use-what.html
@ben Yeah I permanently disabled zram when adding the 8G swap. Will take a look at that article though - thanks
I've now contained both the web browser (8GiB) and slack (2GiB) on my primary laptop via cgroups (as well as the CPU core segregation I already had) in an attempt to avoid the system running out of memory when running larger builds alongside normal desktop application usage. Let's see if there are any negative effects from this.
So far everything is still feeling responsive 🤞
Also thanks to @ben for pointing me at this zswap vs zram article https://fosstodon.org/@ben@hardill.me.uk/116664562204657948