not so much related to ram, but i just did a systemd-analyze to see if i could get rid this problem.
systemd-analyze:
Summary
Startup finished in 2.183s (firmware) + 2.615s (loader) + 4.363s (kernel) + 8.657s (userspace) = 17.820s
graphical.target reached after 8.443s in userspace
systemd-analyze blame:
Summary
systemd-analyze blame
7.521s systemd-networkd-wait-online.service
1.860s systemd-random-seed.service
1.442s upower.service
1.060s systemd-logind.service
713ms dev-sda3.device
594ms udisks2.service
422ms systemd-timesyncd.service
320ms systemd-udevd.service
318ms systemd-networkd.service
318ms systemd-journald.service
211ms tlp.service
197ms polkit.service
192ms ldconfig.service
189ms boot-efi.mount
159ms ufw.service
120ms systemd-udev-trigger.service
95ms avahi-daemon.service
94ms user@1000.service
70ms NetworkManager.service
63ms lm_sensors.service
48ms systemd-fsck@dev-disk-by\xxx…service
45ms systemd-tmpfiles-clean.service
42ms systemd-fsck@dev-disk-by\xxx…service
37ms dev-disk-by\xxx…swap
34ms systemd-fsck@dev-disk-by\xxx…service
29ms systemd-modules-load.service
27ms home.mount
25ms systemd-journal-flush.service
any chance to optimize (or even disable) the first entry for an improved bootup?