systemd-analyze blame
5.710s ModemManager.service
4.616s NetworkManager-wait-online.service
4.499s lvm2-monitor.service
3.319s nmb.service
3.217s dev-sda2.device
3.082s udisks2.service
2.836s polkit.service
2.525s NetworkManager.service
2.523s nfs-idmapd.service
2.372s grub-boot-indeterminate.service
2.335s avahi-daemon.service
2.325s gssproxy.service
2.323s systemd-logind.service
1.595s systemd-journal-flush.service
1.478s systemd-udevd.service
1.249s systemd-tmpfiles-clean.service
987ms tlp.service
637ms smb.service
622ms proc-fs-nfsd.mount
617ms systemd-modules-load.service
545ms org.cups.cupsd.service
542ms
user@1000.service
526ms systemd-tmpfiles-setup-dev.service
508ms systemd-journald.service
447ms rpcbind.service
441ms rpc-statd.service
334ms systemd-udev-trigger.service
332ms upower.service
317ms systemd-random-seed.service
299ms dev-hugepages.mount
298ms dev-mqueue.mount
296ms sys-kernel-debug.mount
254ms nfs-server.service
232ms nfs-mountd.service
204ms nfsdcld.service
179ms systemd-tmpfiles-setup.service
167ms systemd-user-sessions.service
124ms systemd-binfmt.service
107ms dev-disk-by\x2duuid-c33e31f3\x2d41a1\x2d4040\x2d884b\x2dc3b37dcd38e1.swap
95ms systemd-sysctl.service
81ms kmod-static-nodes.service
70ms systemd-update-utmp.service
system-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 @18.254s
└─multi-user.target @18.250s
└─ModemManager.service @7.116s +5.710s
└─basic.target @7.069s
└─paths.target @7.068s
└─org.cups.cupsd.path @7.068s
└─sysinit.target @6.980s
└─systemd-update-utmp.service @6.909s +70ms
└─systemd-tmpfiles-setup.service @6.719s +179ms
└─local-fs.target @6.716s
└─local-fs-pre.target @6.716s
└─lvm2-monitor.service @2.217s +4.499s
└─lvm2-lvmetad.service @2.515s
└─systemd-journald.socket @2.208s
└─system.slice @2.020s
└─-.slice @2.020s