Description of problem:
On netinstall and dvd Fedora ISO install media, zram.service is enabled by default. On LiveOS it's not, but probably would benefit from it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot Fedora-Workstation-Live-x86_64-28_Beta-1.1.iso
2. systemctl status zram.service
Loaded: loaded (/usr/lib/systemd/system/zram.service; static; vendor preset: disabled)
Maybe add a line to the service
This makes sure it's only triggered on live boots not on installed systems?
This really should be enabled. Depending on OOM killer in low memory situations is definitely resulting in a bad experience. This service is enabled by default on netinstalls, but for some reason not lives, and it's even more needed for lives which have a much higher memory footprint.
Proposed as a Freeze Exception for 29-beta by Fedora user chrismurphy using the blocker tracking app because:
In low memory (2GB or less) situations it substantially improves the experience with better performance and far less likely OOM killer instances.
zram.service is enabled on netinstall since at least Fedora 28; and I've been testing it in lives by manually starting it, since Fedora 28. So I'm confident this is safe. This FE request is only to enable zram.service in lives, ensuring it is not enabled on installed systems.
Workstation WG issue:
Although I am +1 FE, I'm confident enough in the behavior of zram.service that we don't really need wide spread beta testing, but it can't hurt to do so.
Summary for the blocker/FE review:
Install environments typically have no swap available until the installer creates and activates it *after* "Begin Installation" is clicked. The zram.service creates a RAM drive that uses LZ4 compression, as swap. The service setup is all user space driven, but the zram block device code is all in the kernel including dynamic allocation, meaning other than 0.1% overhead for creating the zram device, it doesn't actually use any memory until something uses it (i.e. swap is needed).
Further, this does not actually change anything in the installer, it's just that anaconda owns the zram.service and zramswapon scripts that set this up. In fact it will be systemd that will start the service during startup.
Anaconda is not responsible for starting the zram.service in Live OS. However, it might be enough to update the kickstart file for Fedora Live Workstation. Reassigning to LiveCD.