Bug 1562278

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:
https://pagure.io/fedora-workstation/issue/75

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.

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

...Chris, status update?