$ systemd-analyze critical-chain snapd.service 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.
snapd.service +12.817s └─basic.target @2.641s └─sockets.target @2.641s └─snapd.socket @2.637s +2ms └─sysinit.target @2.617s └─systemd-timesyncd.service @2.347s +268ms └─systemd-tmpfiles-setup.service @2.324s +20ms └─local-fs.target @2.316s └─boot-efi.mount @2.306s +8ms └─systemd-fsck@dev-disk-by\x2duuid-DEA6\x2dE70F.service @1.871s +428ms └─dev-disk-by\x2duuid-DEA6\x2dE70F.device @1.806s
$ systemd-analyze critical-chain snapd.service
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.
snapd.service +12.817s ─sysinit. target @2.617s
└─systemd- timesyncd. service @2.347s +268ms
└─systemd- tmpfiles- setup.service @2.324s +20ms
└─ local-fs. target @2.316s
└─boot- efi.mount @2.306s +8ms
└─systemd- fsck@dev- disk-by\ x2duuid- DEA6\x2dE70F. service @1.871s +428ms
└─dev- disk-by\ x2duuid- DEA6\x2dE70F. device @1.806s
└─basic.target @2.641s
└─sockets.target @2.641s
└─snapd.socket @2.637s +2ms
└