I just installed Fedora IoT edition for the first time, version 33, and was surprised that by default there was no swap to compressed memory. I understand that other Fedora editions have been enabling this, and it seems like something that would be of particular benefit to small devices with slow storage.
It was straightforward to enable this myself (rpm-ostree install zram-generator-defaults), but I wondered if it was an oversight that this is not installed by default?
I just installed Fedora IoT edition for the first time, version 33, and was surprised that by default there was no swap to compressed memory. I understand that other Fedora editions have been enabling this, and it seems like something that would be of particular benefit to small devices with slow storage.
It was straightforward to enable this myself (rpm-ostree install zram-generator-defaults), but I wondered if it was an oversight that this is not installed by default?
Yes, that was my fault and an oversight by me, we actually shipped zram from the outset on IoT and when I removed it I had thought that the zram-generator was automatically pulled in as a dep but foolishly didn't check, it will be fixed in the next compose but I had been holding off doing a new f33 compose due to a bug in ostree.
Short story is it's known and should be fixed next week.
P
On Fri, Feb 12, 2021 at 7:07 PM Peter Robinson pbrobinson@gmail.com wrote:
I just installed Fedora IoT edition for the first time, version 33, and was surprised that by default there was no swap to compressed memory. I understand that other Fedora editions have been enabling this, and it seems like something that would be of particular benefit to small devices with slow storage.
It was straightforward to enable this myself (rpm-ostree install zram-generator-defaults), but I wondered if it was an oversight that this is not installed by default?
Yes, that was my fault and an oversight by me, we actually shipped zram from the outset on IoT and when I removed it I had thought that the zram-generator was automatically pulled in as a dep but foolishly didn't check, it will be fixed in the next compose but I had been holding off doing a new f33 compose due to a bug in ostree.
Short story is it's known and should be fixed next week.
This should be fixed in today's compose, let me know how you get on.