Quantify boot phases and isolate slow services with simple commands. 17.01.2026 | reading time: 2 min Boot feels slow: where does time go? Use systemd utilities to split kernel and userspace startup, then hunt the heaviest services and fix them. Hands-on Example Run these commands on a systemd system to see concrete numbers and a service breakdown: ```sudo systemd-analyze time Startup finished in 1.203s (kernel) + 2.512s (userspace) = 3.715s sudo systemd-analyze blame 3.842s NetworkManager.service 1.234s plymouth-quit.service 0.980s dev-sda1.device 0.456s sshd.service sudo systemd-analyze critical-chain graphical.target @3.842s └─multi-user.target @3.842s └─NetworkManager.service @0.456s +3.386s └─sshd.service @0.980s +0.456s ``` Where To Look Next If a service dominates, inspect its unit file and dependencies; use `systemd-analyze plot` to generate an SVG timeline, and check `journalctl -b` and `dmesg -T` for kernel and early-boot messages; remember to compare cold boots and reboots because firmware/firmware drivers can add time. Alternative Views Not every system uses systemd; `dmesg` reveals kernel boot timestamps, `journalctl` exposes userspace logs, bootchart and eBPF tracers give deeper timelines, and simple `uptime` or log-based measurements help in virtualized environments. Finish Line Measuring boot time is a practical way to make systems feel faster and more reliable; keep experimenting, document fixes, and expand skills—consider intensive exam preparation at bitsandbytes.academy for CompTIA Linux+ or LPIC-1 to make it official. Join Bits & Bytes Academy First class LINUX exam preparation. boot-process troubleshooting utilities processes infrastructure
