This is from a cosmic GCE instance _before_ the lxd snap was seeded (i.e. with just the google-cloud-sdk snap seeded):
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
This is from a cosmic GCE instance _before_ the lxd snap was seeded (i.e. with just the google-cloud-sdk snap seeded):
$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @15.614s ─sockets. target @7.466s
└─snapd. socket @7.076s +305ms
└─sysinit. target @6.806s
└─ cloud-init. service @4.715s +2.013s
└─systemd- networkd- wait-online. service @3.136s +1.575s
└─systemd- networkd. service @3.007s +109ms
└─network- pre.target @2.994s
└ ─cloud- init-local. service @802ms +2.181s
└─systemd- remount- fs.service @634ms +152ms
└─systemd- journald. socket @454ms
└─ -.mount @425ms
└─system. slice @425ms
└─-.slice @425ms
└─multi-user.target @15.614s
└─chrony.service @16.650s +56ms
└─basic.target @7.478s
└
$ journalctl --boot 0 | pastebinit paste.ubuntu. com/p/Xj9wzRhQr b/
http://
$ ps fauxww | pastebinit paste.ubuntu. com/p/TgK2FRW3K N/
http://