Post your Systemd startup times


Okay after a bit of fluffing around I managed to deal with the man-db that was holding everything up

Take a squiz at this:

Startup finished in 2.131s (kernel) + 3.077s (userspace) = 5.209s reached after 3.077s in userspace


So what did you end up doing; some of the tips from the thread pangolin posted?


Yup, followed his link. And it worked perfectly.


With my (very) old Toshiba A300 :

Startup finished in 2.446s (kernel) + 2.799s (userspace) = 5.246s reached after 2.762s in userspace

(But I have a ssd ; even with SATA2 it helps)

      1.377s lvm2-monitor.service
      1.234s dev-sda5.device
       532ms upower.service
       450ms NetworkManager.service
       431ms udisks2.service
       302ms systemd-rfkill.service
       275ms lightdm.service
       254ms systemd-udev-trigger.service
       233ms systemd-journal-flush.service
       209ms accounts-daemon.service
       179ms systemd-journald.service
       176ms laptop-mode.service
       142ms polkit.service
       140ms systemd-fsck@dev-disk-by\x2duuid-79757b64\x2d67d0\x2d461b\x2d823d\x2d800cf6e8bfe8.service
       109ms systemd-logind.service
       106ms systemd-udevd.service
        95ms user@1000.service
        93ms systemd-remount-fs.service
        81ms systemd-modules-load.service
        81ms mnt-sauvegardes.mount
        73ms kmod-static-nodes.service
        68ms systemd-fsck@dev-disk-by\x2duuid-0df78367\x2d5dfd\x2d48e9\x2db62f\x2d2a1b0fb3e523.service
        67ms systemd-sysctl.service
        63ms dev-mqueue.mount
        63ms dev-hugepages.mount
        58ms systemd-backlight@backlight:acpi_video0.service
        55ms wpa_supplicant.service
        53ms systemd-random-seed.service
        44ms sys-kernel-debug.mount
        37ms ntpd.service
        37ms systemd-tmpfiles-clean.service
        36ms sys-kernel-config.mount
        31ms systemd-tmpfiles-setup.service
        30ms systemd-tmpfiles-setup-dev.service
        23ms home.mount
        19ms sys-fs-fuse-connections.mount
        15ms systemd-update-utmp.service
        13ms dev-disk-by\x2duuid-f44b7514\x2dabdb\x2d43b1\x2d8d62\x2d726a5f3489d4.swap
        11ms systemd-user-sessions.service
        10ms tmp.mount
         4ms rtkit-daemon.service



Startup finished in 13.736s (firmware) + 6.121s (loader) + 3.442s (kernel) + 14.467s (userspace) = 37.767s reached after 14.467s in userspace

And here’s my blame.

7.269s lvm2-monitor.service
7.153s dev-sda2.device
2.272s NetworkManager.service
2.170s systemd-journal-flush.service
1.422s systemd-logind.service
1.421s bluetooth.service
1.347s systemd-udevd.service
1.058s ldconfig.service
917ms systemd-sysusers.service
838ms polkit.service
666ms wpa_supplicant.service
658ms sys-kernel-debug.mount
623ms systemd-update-utmp.service
592ms lightdm.service
566ms systemd-journal-catalog-update.service
539ms user@1000.service
492ms udisks2.service
457ms dev-mqueue.mount
443ms systemd-remount-fs.service
414ms dev-hugepages.mount
397ms swapfile.swap
359ms org.cups.cupsd.service
350ms systemd-modules-load.service
350ms kmod-static-nodes.service
319ms rtkit-daemon.service
307ms sys-kernel-config.mount
277ms systemd-tmpfiles-setup-dev.service
263ms systemd-fsck@dev-disk-by\x2duuid-8309\x2d5C12.service

I am also running on an HDD.


Mine have turned to shit again

'Startup finished in 2.156s (kernel) + 1min 45.911s (userspace) = 1min 48.068s reached after 2.767s in userspace


^ If I had to guess I would point the finger at journalctl, it’s a lovely tool but it can hog the boot if the files get large.

This can give a better breakdown:

systemd-analyze critical-chain

Or perhaps even:

systemd-analyze plot > boot.svg

I’m not booted under systemd at the moment, I’ll post my time next time I am.


Looks like this:

─lvm2-monitor.service @254ms +1.221s

is the culprit, though boot.svg shows that updatedb.service is the issue @ approx 1min 44.


Startup finished in 7.369s (firmware) + 6.902s (loader) + 2.537s (kernel) + 30.393s (userspace) = 47.202s reached after 15.121s in userspace

19.474s man-db.service
7.451s dev-sda2.device
7.073s lvm2-monitor.service
4.587s systemd-journal-flush.service
3.372s NetworkManager.service
3.276s systemd-udevd.service
1.643s bluetooth.service
1.638s systemd-logind.service
1.219s upower.service
1.131s ldconfig.service
1.089s systemd-rfkill.service
1.027s systemd-sysusers.service
976ms systemd-backlight@backlight:intel_backlight.service
826ms polkit.service
798ms lightdm.service
520ms systemd-journal-catalog-update.service
473ms systemd-udev-trigger.service
435ms systemd-hostnamed.service
420ms systemd-tmpfiles-setup-dev.service
416ms systemd-tmpfiles-setup.service
407ms ntpd.service
405ms org.cups.cupsd.service
386ms sys-kernel-debug.mount
354ms wpa_supplicant.service
337ms udisks2.service
331ms systemd-modules-load.service
330ms systemd-remount-fs.service
312ms systemd-sysctl.service
243ms systemd-fsck@dev-disk-by\x2duuid-FBE9\x2d7603.service
226ms systemd-random-seed.service
223ms systemd-tmpfiles-clean.service
177ms systemd-journald.service
168ms tmp.mount
101ms systemd-update-utmp.service
98ms kmod-static-nodes.service
92ms dev-mqueue.mount
90ms boot-efi.mount
90ms dev-hugepages.mount
54ms user@1000.service
41ms systemd-user-sessions.service
24ms systemd-update-done.service
18ms rtkit-daemon.service
5ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount

i3-6006u,4GB DDR4,HDD


‘pretty-much fresh install’ on a Thinkpad:

pitje@thinkpitje ~ % systemd-analyze && systemd-analyze blame
Startup finished in 4.497s (firmware) + 1.525s (loader) + 784ms (kernel) + 814ms (userspace) = 7.621s reached after 812ms in userspace
          1.262s man-db.service
           335ms lvm2-monitor.service
           242ms dev-nvme0n1p2.device
           173ms NetworkManager.service
            92ms systemd-rfkill.service
            85ms upower.service
            68ms systemd-udev-trigger.service
            59ms systemd-fsck@dev-disk-by\x2duuid-9f1b1044\x2d5296\x2d4fd9\x2da075\x2d23c5fab2d44a.service
            57ms systemd-journald.service
            53ms systemd-journal-flush.service
            50ms udisks2.service
            49ms boot-efi.mount
            44ms systemd-logind.service
            37ms systemd-fsck@dev-disk-by\x2duuid-13CA\x2d2144.service
            30ms systemd-tmpfiles-setup.service
            29ms systemd-udevd.service
            27ms user@1000.service
            27ms lightdm.service
            27ms polkit.service
            21ms geoclue.service
            20ms home.mount
            20ms systemd-modules-load.service
            18ms systemd-tmpfiles-setup-dev.service
            18ms systemd-update-utmp.service
            16ms logrotate.service
            14ms bluetooth.service
            13ms dev-disk-by\x2duuid-761c5dc0\x2d6a4e\x2d4b09\x2dbb29\x2d30e52e9acb63.swap
            12ms dev-mqueue.mount
            12ms kmod-static-nodes.service
            11ms dev-hugepages.mount
            10ms systemd-random-seed.service
            10ms systemd-tmpfiles-clean.service
            10ms systemd-remount-fs.service
             9ms ntpd.service
             9ms sys-kernel-debug.mount
             8ms wpa_supplicant.service
             7ms systemd-sysctl.service
             7ms systemd-user-sessions.service
             7ms systemd-backlight@backlight:intel_backlight.service
             6ms systemd-backlight@leds:tpacpi::kbd_backlight.service
             6ms tmp.mount
             5ms sys-kernel-config.mount
             3ms sys-fs-fuse-connections.mount
             3ms rtkit-daemon.service

empty@animal:~ $ systemd-analyze                                                             
Startup finished in 3.587s (kernel) + 1.798s (userspace) = 5.385s
empty@animal:~ $ systemd-analyze blame --no-pager                                            
          1.637s networking.service
           254ms dev-sda6.device
            98ms loadcpufreq.service
            81ms keyboard-setup.service
            57ms systemd-journald.service
            42ms upower.service
            38ms systemd-udev-trigger.service
            34ms systemd-logind.service
            28ms lm-sensors.service
            27ms systemd-rfkill.service
            25ms alsa-restore.service
            25ms systemd-tmpfiles-setup.service
            23ms user@1000.service
            22ms systemd-udevd.service
            19ms dev-sda3.swap
            16ms ntp.service
            16ms systemd-tmpfiles-clean.service
            12ms console-setup.service
            11ms systemd-tmpfiles-setup-dev.service
            10ms systemd-backlight@backlight:intel_backlight.service
             8ms systemd-journal-flush.service
             8ms systemd-random-seed.service
             7ms systemd-remount-fs.service
             7ms cpufrequtils.service
             7ms hddtemp.service
             7ms dev-mqueue.mount
             7ms polkit.service
             6ms systemd-modules-load.service
             6ms kmod-static-nodes.service
             6ms dev-hugepages.mount
             6ms systemd-sysctl.service
             6ms systemd-update-utmp.service
             4ms systemd-update-utmp-runlevel.service
             3ms systemd-user-sessions.service
             2ms sys-kernel-debug.mount
empty@animal:~ $

(BunsenLabs Helium, i5-4330M with a Samsung EVO 850 SSD)


northman@archmac ~ % systemd-analyze
Startup finished in 1.912s (kernel) + 1.187s (userspace) = 3.099s reached after 1.187s in userspace

northman@archmac ~ % systemd-analyze blame
345ms lvm2-monitor.service
290ms systemd-fsck@dev-disk-by\x2duuid-8f1f9d61\x2dae52\x2d4a7b\x2d90e6\x2d183266780de1.service
189ms systemd-logind.service
178ms NetworkManager.service
151ms home.mount
145ms boot-efi.mount
142ms systemd-fsck@dev-disk-by\x2duuid-67E3\x2d17ED.service
135ms dev-nvme0n1p1.device
68ms systemd-rfkill.service
62ms systemd-udev-trigger.service
57ms lightdm.service
48ms bluetooth.service
47ms systemd-journald.service
37ms udisks2.service
37ms user@1000.service
36ms systemd-journal-flush.service
21ms systemd-tmpfiles-clean.service
21ms polkit.service
18ms systemd-tmpfiles-setup.service
16ms systemd-udevd.service
15ms systemd-sysctl.service
11ms systemd-update-utmp.service
10ms systemd-tmpfiles-setup-dev.service
10ms systemd-modules-load.service
10ms systemd-remount-fs.service
10ms org.cups.cupsd.service
9ms dev-mqueue.mount
8ms systemd-random-seed.service
8ms ntpd.service
8ms kmod-static-nodes.service
7ms dev-hugepages.mount
6ms sys-kernel-debug.mount
6ms wpa_supplicant.service
5ms sys-kernel-config.mount
4ms tmp.mount
4ms systemd-backlight@backlight:acpi_video0.service
3ms systemd-user-sessions.service
3ms sys-fs-fuse-connections.mount
3ms systemd-backlight@backlight:amdgpu_bl0.service
2ms rtkit-daemon.service

empty@stretch:~$ systemd-analyze 
Startup finished in 212ms (kernel) + 192ms (userspace) = 404ms
empty@stretch:~$ systemd-analyze blame --no-pager
            92ms keyboard-setup.service
            72ms dev-vda1.device
            44ms networking.service
            40ms systemd-udev-trigger.service
            24ms ssh.service
            20ms user@1000.service
            16ms systemd-logind.service
            16ms kmod-static-nodes.service
            16ms dev-hugepages.mount
            16ms systemd-remount-fs.service
            16ms systemd-journald.service
            12ms systemd-sysctl.service
            12ms rsyslog.service
            12ms systemd-random-seed.service
            12ms systemd-tmpfiles-setup.service
            12ms systemd-journal-flush.service
            12ms systemd-udevd.service
            12ms systemd-tmpfiles-setup-dev.service
            12ms dev-mqueue.mount
            12ms sys-kernel-debug.mount
            12ms systemd-update-utmp.service
             8ms systemd-user-sessions.service
             8ms console-setup.service
             4ms systemd-modules-load.service
             4ms systemd-timesyncd.service
             4ms systemd-update-utmp-runlevel.service

Do I win?


What the? 404ms?


^ I’m cheating :smiley:

It’s from a virtual machine running under OpenBSD’s hypervisor:

*runs away giggling madly*


Okay thats as bad as the Aussie Crickters and their ball tampering @Head_on_a_Stick. :slight_smile: :cricket_bat_and_ball:


This is mine.

andy@Neuromancer  ~  systemd-analyze
Startup finished in 1.858s (kernel) + 1.114s (userspace) = 2.972s reached after 1.113s in userspace

Hmm,using the agnoster theme,and it’s not copy/pasting very nicely!


Startup finished in 9.591s (firmware) + 5.262s (loader) + 1.061s (kernel) + 632ms (userspace) = 16.546s reached after 632ms in userspace

Arch Linux archlabs (Linux 4.15.15-1-ARCH #1 SMP PREEMPT Sat Mar 31 23:59:25 UTC 2018) x86-64

cu, stephan


Well - here’s mine.


Gee, mine takes forever compared to some installs here !From my HP Pavilion craptop.

Startup finished in 3.614s (kernel) + 27.606s (userspace) = 31.220s reached after 27.599s in userspace