Any way to get my laptop to boot faster?

Hello. Is there any way i can get my system to boot faster? It seems pretty slow compared to my windows pc, even with a mostly empty ssd, and i’d really benefit from any extra speed here as i just use this laptop for class.

Here is my systemd-analyze:

Startup finished in 3.120s (firmware) + 4.132s (loader) + 2.342s (kernel) + 3.417s (userspace) = 13.013s
graphical.target reached after 2.402s in userspace

And here is my systemd-analyze blame:

1.246s lvm2-monitor.service
1.151s dev-sda2.device
1.090s apparmor.service
1.012s tlp.service
555ms systemd-random-seed.service
521ms snapd.service
302ms polkit.service
299ms systemd-udev-trigger.service
282ms systemd-rfkill.service
263ms upower.service
205ms systemd-logind.service
201ms avahi-daemon.service
187ms NetworkManager.service
162ms ModemManager.service
151ms user@1000.service
129ms systemd-journal-flush.service
126ms systemd-journald.service
1.246s lvm2-monitor.service
1.246s lvm2-monitor.service
1.151s dev-sda2.device
1.090s apparmor.service
1.012s tlp.service
555ms systemd-random-seed.service
1.246s lvm2-monitor.service
1.151s dev-sda2.device
1.090s apparmor.service
1.012s tlp.service
555ms systemd-random-seed.service
521ms snapd.service
302ms polkit.service
299ms systemd-udev-trigger.service
282ms systemd-rfkill.service
263ms upower.service
205ms systemd-logind.service
201ms avahi-daemon.service
187ms NetworkManager.service
162ms ModemManager.service
151ms user@1000.service
129ms systemd-journal-flush.service
126ms systemd-journald.service
116ms udisks2.service
112ms boot-efi.mount
104ms systemd-udevd.service
98ms modprobe@drm.service
79ms cups.service
73ms systemd-binfmt.service
60ms systemd-modules-load.service
48ms dev-hugepages.mount
47ms dev-mqueue.mount
45ms sys-kernel-debug.mount
44ms kmod-static-nodes.service
44ms sys-kernel-tracing.mount
42ms modprobe@configfs.service
42ms linux-module-cleanup.service
38ms modprobe@fuse.service
37ms systemd-fsck@dev-disk-by\x2duuid-A772\x2dDB03.service
36ms sys-fs-fuse-connections.mount
36ms proc-sys-fs-binfmt_misc.mount
35ms sys-kernel-config.mount
32ms systemd-remount-fs.service
32ms systemd-tmpfiles-setup-dev.service
30ms systemd-tmpfiles-setup.service
24ms user-runtime-dir@1000.service
22ms wpa_supplicant.service
19ms systemd-backlight@backlight:amdgpu_bl0.service
19ms snapd.apparmor.service
15ms tmp.mount
15ms systemd-update-utmp.service
13ms bluetooth.service
10ms rtkit-daemon.service
9ms systemd-sysctl.service
8ms systemd-backlight@backlight:acpi_video0.service
7ms systemd-user-sessions.service
4ms snapd.socket
3ms alsa-restore.service

if not used do uninstall snap and flatpak.

What are they used for in the first place?

They are alternative methods of installing software. If you use the GUI installer, you shouldn’t need them

Hello @princesscat :wink:

So we are talking about 2 different systems? True thing that a PC is mostly faster than a laptop.

What you should consider is that windows 10 uses fast boot, what in general is hibernation. So everytime you shutdown your windows pc, it will hibernate. Hibernation and a full boot are 2 different things.

So we are talking about 15sec boot time? This is not slow, but compared to hibernation, yes, it is slower.

You could mask lvm2-monitor.service (see using systemd units) if you do not need it.
You can also enable caching for AppArmor (see AppArmor caching).
As others stated, disable flatpak and snaps if you do not need them; compare boot times with Windows with fast startup disabled!

I think this is the time spent for Grub even if it is hidden it will wait so you can still have time to make it show with the proper key on boot. You could set it to one second timeout in /etc/default/grub and then sudo update-grub

Also your output from the systemd-analyze blame command is duplicated multiple time in your post.