Which command lists the boot-time impact of each service in order of time spent?

• A. systemd-analyze blame
• B. journalctl
• C. systemd-analyze times
• D. systemd-bootchart

Answer: (A)

When you’re trying to understand boot performance, you want to see which services slow things down. systemd-analyze blame provides exactly that: it lists each unit and the time systemd spent starting it, ordered from the longest to the shortest boot-time impact. This lets you quickly identify the biggest culprits, such as a network service or a storage mount, so you can focus optimization efforts on those first. The output shows lines like a time value followed by the unit name, making it clear which services contribute most to the total boot time.

Other commands don’t give this per-service, time-ordered view. journalctl shows boot logs rather than startup timing per unit. systemd-analyze times gives a global summary of kernel and userspace time (or total boot time) but not the per-service breakdown. systemd-bootchart provides a graphical chart of the boot process, not a simple, ordered list of times per service. If you want the exact boot-time cost by service and in descending order, systemd-analyze blame is the best fit. You can further refine the view with a command like systemd-analyze blame | head to see the top delays.