zswap works well in my experience. Don't need both. Combined with systemd-oomd I haven't had a swapping or memory issue in many years. 16gb here with VMs and lots going on. This doc clears some things up:
That's my whole point: on Linux a process gets killed to prevent a system lock up if you're about to run out of memory or swap. That never happens on macOS, as long as you have some SSD left, period.
That’s not what I want (rogue program swapping until disk full), nor do I think most people want. Current
zswap+oomd behavior is the best choice imho.
OMG why do you keep on insisting on this? The point is you can run as many apps in the background and at no point will they get OOM-ed. This isn't about a rougue app, this is actually a very obscure reason to run out of memory! I get OOMed weekly on Asahi with 16GB only because my Brave/Chromium session grows too big. THIS NEVER HAPPENS ON MACOS.
> Current zswap+oomd behavior is the best choice imho
This isn't up for debate, Linux memory management is less advanced. How about you actually read up on the advantages of how macOS handles the memory and stop the speculation OK?
Either the programs are operating normally, or they aren't. You don't get to pick and choose to suit your argument.
Above someone else is complaining about a browser on asahi. There's obviously a leaking problem but you are uninterested in solving it, just keep repeating "macos more advanced," which is not a useful argument.
The oomd memory pressure threshold is tunable, you know. So are browsers/plugins, etc. As I mentioned I've been using Linux and 16gb RAM since ~2010 and haven't had ooms in the last decade+ since firefox was overhauled.
That's my whole point: on Linux a process gets killed to prevent a system lock up if you're about to run out of memory or swap. That never happens on macOS, as long as you have some SSD left, period.