On Mon, Jan 6, 2020 at 7:56 PM Dusty Mabe <dusty(a)dustymabe.com> wrote:
For cloud at least it's very common to not have swap. I'd argue for servers
you don't want them swapping either but resources aren't quite as elastic as
in the cloud so you might not be able to burst resources like you can in the cloud.
There's also discussion about making oomd a universal solution for
this; but I came across this issue asserting PSI (kernel pressure
stall information) does not work well without swap.
https://github.com/facebookincubator/oomd/issues/80
Ignoring whether+what+when a workaround may be found for that, what do
you think about always having swap-on-ZRAM enabled in these same
environments? The idea there is a configurable size /dev/zram block
device (basically a compressible RAM disk) on which swap is created.
Based on discussions with anaconda, IoT, Workstation, and systemd
folks - I think there's a potential to converge on systemd-zram
generator (rust) to do this.
https://github.com/systemd/zram-generator
Workstation wg is mulling over the idea of dropping separate swap
partitions entirely, and using a swap-on-ZRAM device instead; possibly
with a dynamically created swapfile for certain use cases like
hibernation. So I'm curious if this might have broader appeal, and get
systemd-zram generator production ready.
--
Chris Murphy