TIL You can use `systemd-analyze plot > plot.svg` to plot the service startup time to find bottlenecks

Pantherina, 9 months ago

My bottleneck at boot is my damn Bios… I am so hyped about flashing Heads on my Thinkpad T430.

Even the old legacy Lenovo bioses where very fast at startup. The UEFI (with extremely nice secure-boot settings too) of an AMD Acer starts up in like 2 seconds. My old intel Thinkpad T430 needs like 4 seconds.

And then my Lenovo T495 bullshit UEFI comes. No secure boot configuration at all, I have no idea how to boot from USB sticks, and this thing needs nearly 10 seconds to boot! Linux compared, a full Desktop OS, needs 3 seconds to show SDDM (after the LUKS dialog)

Pantherina, 9 months ago

Systemd can generate SVGs? Damn thats “bloat” but also unexpectedly fancy

vsh, 9 months ago

How do you read this?

stifle867, 9 months ago

The top/1st line is the first service and it cascaded down as each subsequent service starts. Left to right is time elapsed. Bright red line is time to start that service. Shorter is better.

Does that help?

jsdz, 9 months ago

I’m pretty sure the main system startup bottleneck is me typing the disk encryption passphrase.

germanatlas, 9 months ago

the only “bottleneck” i currently have is plymouth-quit-wait.service, which takes 3.9 seconds. i can live with that

passepartout, 9 months ago

You can use systemd-analyze blame if you want raw numbers:

This command prints a list of all running units, ordered by the time they took to initialize. This information may be used to optimize boot-up times.

Good way to see if your systemd also waits 2 minutes for a network connection which already exists but it can’t see it because systemd doesn’t do the networking (lxc containers on proxmox in my case) lol.

Also see systemd-analyze.