You are not logged in.
My arch installation is near 10 years old. But it is updated, cleaned and mantained by me regulary.
I have installed new WD SN770 NVME this week and pc boot time is:
# systemd-analyze
Startup finished in 10.638s (firmware) + 332ms (loader) + 6.856s (kernel) + 5.807s (userspace) = 23.634s
graphical.target reached after 5.771s in userspace.# systemd-analyze blame
3.037s netctl@wired_mcc.service
766ms dev-nvme0n1p2.device
435ms systemd-fsck@dev-disk-by\x2duuid-08edbb1d\x2da2d3\x2d4ed0\x2d8685\x2d4be0394720f1.service
393ms udisks2.service
332ms systemd-udev-trigger.service
299ms systemd-remount-fs.service
273ms systemd-modules-load.service
245ms lvm2-monitor.service
218ms systemd-tmpfiles-setup.service
169ms systemd-tmpfiles-setup-dev.service
169ms systemd-fsck@dev-disk-by\x2duuid-973e36bf\x2d4c6e\x2d42f9\x2da7ef\x2d11302e07d7b3.service
136ms modprobe@fuse.service
135ms systemd-sysctl.service
128ms home-public.mount
105ms user@1001.service
99ms systemd-journal-flush.service
95ms user-runtime-dir@1001.service
85ms systemd-boot-random-seed.service
85ms avahi-daemon.service
80ms lm_sensors.service
78ms upower.service
71ms systemd-user-sessions.service
70ms lightdm.service
68ms systemd-journald.service
64ms boot.mount
63ms mnt-ssd.mount
59ms systemd-fsck@dev-nvme0n1p1.service
53ms systemd-binfmt.service
49ms geoclue.service
49ms cups.service
47ms modprobe@loop.service
44ms systemd-random-seed.service
43ms systemd-timesyncd.service
42ms systemd-update-utmp.service
41ms accounts-daemon.service
39ms systemd-tmpfiles-clean.service
38ms kmod-static-nodes.service
38ms modprobe@configfs.service
35ms systemd-logind.service
33ms bluetooth.service
30ms alsa-restore.service
29ms systemd-udevd.service
29ms dbus.service
16ms colord.service
15ms openvpn-client@sb117.service
15ms power-profiles-daemon.service
14ms sys-kernel-config.mount
13ms sys-fs-fuse-connections.mount
9ms dev-hugepages.mount
9ms polkit.service
9ms dev-mqueue.mount
9ms sys-kernel-debug.mount
8ms sys-kernel-tracing.mount
8ms tmp.mount
6ms wpa_supplicant.service
4ms modprobe@drm.service
3ms rtkit-daemon.service
3ms systemd-rfkill.service
1ms proc-sys-fs-binfmt_misc.mount
1ms modprobe@dm_mod.service# 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 @5.771s
└─lightdm.service @5.699s +70ms
└─systemd-user-sessions.service @5.625s +71ms
└─nss-user-lookup.target @5.708sIs this normal? Or it can be faster?
Offline
I have nvme ssd drives also and boot times are not dissimilar to yours. On two different machines both ryzen, with one 5700 I have:
$ systemd-analyze
Startup finished in 4.974s (firmware) + 2.407s (loader) + 1.884s (kernel) + 1.316s (initrd) + 11.465s (userspace) = 22.047s
graphical.target reached after 11.465s in userspace.and
$ systemd-analyze
Startup finished in 4.428s (firmware) + 4.240s (loader) + 2.608s (kernel) + 3.592s (initrd) + 7.455s (userspace) = 22.325s
graphical.target reached after 7.454s in userspace.Mike C
Offline
I have on my old Pentium Dual Core E2140 with ssd working like sata2:
$ systemd-analyze
Startup finished in 4.545s (kernel) + 3.575s (userspace) = 8.120s
graphical.target reached after 3.353s in userspace.but I cheating a bit...
Offline