[int13h@homepc test]$ systemd-analyze blame
193ms dev-sda1.device
93ms systemd-journald.service
44ms systemd-hostnamed.service
35ms lm_sensors.service
31ms systemd-udevd.service
31ms systemd-udev-trigger.service
27ms polkit.service
25ms systemd-resolved.service
23ms systemd-journal-flush.service
21ms upower.service
20ms systemd-tmpfiles-setup-dev.service
17ms systemd-logind.service
17ms systemd-networkd.service
16ms user@1000.service
8ms kmod-static-nodes.service
7ms systemd-vconsole-setup.service
7ms var-tmp.mount
7ms systemd-user-sessions.service
6ms var-cache.mount
5ms systemd-tmpfiles-setup.service
5ms systemd-remount-fs.service
5ms var-log.mount
5ms tmp.mount
5ms systemd-sysctl.service
5ms systemd-random-seed.service
4ms sys-kernel-debug.mount
4ms rtkit-daemon.service
3ms sys-kernel-config.mount
2ms systemd-update-utmp.service
2ms dev-mqueue.mount
2ms dev-hugepages.mount
2ms systemd-backlight@backlight:acpi_video0.service
1ms home-int13h-.cache.mount
[int13h@homepc test]$ systemd-analyze
Startup finished in 2.172s (kernel) + 309ms (userspace) = 2.481s
[int13h@homepc test]$ 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 @309ms
`-multi-user.target @308ms
`-systemd-resolved.service @283ms +25ms
`-network.target @282ms
`-systemd-networkd.service @264ms +17ms
`-dbus.service @229ms
`-basic.target @229ms
`-sockets.target @229ms
`-dbus.socket @228ms
`-sysinit.target @228ms
`-systemd-update-utmp.service @225ms +2ms
`-systemd-tmpfiles-setup.service @218ms +5ms
`-systemd-journal-flush.service @194ms +23ms
`-systemd-journald.service @95ms +93ms
`-systemd-journald.socket @83ms
`--.mount @76ms
`-system.slice @79ms
`--.slice @76ms
[int13h@homepc test]$
Я доволен. Можно ли еще улучшить?
