Wie man die Bootzeiten eines Linuxsystems mit systemd analysiert…
$ sudo systemd-analyze time
Startup finished in 8.618s (firmware) + 2.628s (loader) + 2.943s (kernel) + 8.948s (userspace) = 23.139s
graphical.target reached after 8.948s in userspace
mplx at linuxdesktop in ~
$ sudo 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.948s
└─multi-user.target @8.948s
└─docker.service @7.913s +1.033s
└─network-online.target @7.912s
└─NetworkManager-wait-online.service @2.588s +5.323s
└─NetworkManager.service @2.529s +58ms
└─network-pre.target @2.528s
└─ip6tables.service @2.509s +19ms
└─iptables.service @2.502s +6ms
└─basic.target @2.496s
└─sockets.target @2.496s
└─docker.socket @2.496s +734us
└─sysinit.target @2.492s
└─systemd-update-done.service @2.486s +5ms
└─ldconfig.service @2.073s +412ms
└─local-fs.target @2.072s
└─var-lib-docker-btrfs.mount @8.472s
└─local-fs-pre.target @1.711s
└─lvm2-monitor.service @419ms +1.292s
└─lvm2-lvmetad.service @431ms
└─systemd-journald.socket @415ms
└─-.mount @398ms
└─system.slice @398ms
└─-.slice @398ms
$ sudo systemd-analyze blame | head
5.323s NetworkManager-wait-online.service
2.339s etckeeper.service
1.550s man-db.service
1.292s lvm2-monitor.service
1.270s dev-sdb4.device
1.033s docker.service
481ms systemd-journal-flush.service
469ms updatedb.service
412ms ldconfig.service
388ms systemd-udevd.service