$ 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.084s
└─multi-user.target @8.084s
└─plymouth-quit-wait.service @6.019s +2.044s
└─systemd-user-sessions.service @5.938s +62ms
└─remote-fs.target @5.935s
└─remote-fs-pre.target @3.120s
└─nfs-client.target @3.120s
└─gssproxy.service @3.108s +11ms
└─network.target @3.094s
└─wpa_supplicant.service @3.719s +5ms
└─basic.target @2.294s
└─dbus-broker.service @2.262s +30ms
└─dbus.socket @2.255s
└─sysinit.target @2.246s
└─systemd-update-utmp.service @2.217s +28ms
└─auditd.service @2.048s +131ms
└─systemd-tmpfiles-setup.service @1.792s +237ms
└─local-fs.target @1.763s
└─usr-lib-waydroid.mount @2.704s
└─dev-nvme0n1p3.device @584542y 2w 2d 20h 43.461s +1min 7.495s
$ 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.084s
└─multi-user.target @8.084s
└─plymouth-quit-wait.service @6.019s +2.044s
└─systemd-user-sessions.service @5.938s +62ms
└─remote-fs.target @5.935s
└─remote-fs-pre.target @3.120s
└─nfs-client.target @3.120s
└─gssproxy.service @3.108s +11ms
└─network.target @3.094s
└─wpa_supplicant.service @3.719s +5ms
└─basic.target @2.294s
└─dbus-broker.service @2.262s +30ms
└─dbus.socket @2.255s
└─sysinit.target @2.246s
└─systemd-update-utmp.service @2.217s +28ms
└─auditd.service @2.048s +131ms
└─systemd-tmpfiles-setup.service @1.792s +237ms
└─local-fs.target @1.763s
└─usr-lib-waydroid.mount @2.704s
└─dev-nvme0n1p3.device @584542y 2w 2d 20h 43.461s +1min 7.495s
©
A
N
K
A
