I have enabled zram using the zram-generator package from the repos and setting it to ram/2
The boot time is much longer now. I’ll post the comparison below:
Before zram
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @8.881s
└─multi-user.target @8.880s
└─tailscaled.service @7.486s +1.393s
└─NetworkManager.service @7.284s +151ms
└─network-pre.target @7.270s
└─firewalld.service @5.532s +1.724s
└─polkit.service @5.544s +87ms
└─basic.target @5.396s
└─sockets.target @5.394s
└─dbus.socket @5.393s
└─sysinit.target @5.329s
└─systemd-resolved.service @4.959s +361ms
└─systemd-tmpfiles-setup.service @4.600s +282ms
└─systemd-journal-flush.service @3.623s +873ms
└─var-log.mount @3.187s +144ms
└─dev-mmcblk2p2.device @584ms +2.519s
After enabling zram
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @55.205s
└─multi-user.target @55.204s
└─tailscaled.service @53.831s +1.371s
└─NetworkManager.service @53.605s +187ms
└─network-pre.target @53.598s
└─firewalld.service @51.986s +1.608s
└─polkit.service @52.008s +96ms
└─basic.target @51.741s
└─sockets.target @51.739s
└─dbus.socket @51.737s
└─sysinit.target @51.663s
└─systemd-resolved.service @51.282s +370ms
└─systemd-tmpfiles-setup.service @50.910s +242ms
└─systemd-journal-flush.service @50.219s +672ms
└─var-log.mount @50.186s +22ms
└─dev-mmcblk2p2.device @49.405s +761ms
Any ideas on what is happening here?
