Post your Systemd startup times


#1

Share your systemd startup times.

To do this, in a terminal for startup times:

systemd-analyze

To see what is starting up, in a terminal:

systemd-analyze blame

Or to view in graph:

systemd-analyze plot > boot.svg


#2

Today mine is a little crap:

Startup finished in 2.196s (kernel) + 1min 5.264s (userspace) = 1min 7.460s
graphical.target reached after 2.819s in userspace

The blame goes to:

1min 2.681s updatedb.service
3.368s man-db.service
1.222s lvm2-monitor.service
803ms run-media-dobbie-Time\x20Machine.mount
764ms dev-disk-by\x2duuid-a9de30d6\x2ddd5e\x2d47a2\x2d8af8\x2ddaf3a73266db.swap
602ms run-media-dobbie-Music.mount
524ms run-media-dobbie-Important.mount
486ms dev-sdc1.device
485ms run-media-dobbie-Movies.mount
306ms systemd-remount-fs.service
301ms systemd-fsck@dev-disk-by\x2duuid-f50f1d01\x2dcc71\x2d4d72\x2dacb6\x2df3d7d70c2e30.service
226ms systemd-hwdb-update.service
216ms NetworkManager.service
192ms systemd-logind.service
169ms systemd-journal-flush.service
167ms ldconfig.service
117ms home.mount
115ms udisks2.service
102ms run-media-dobbie-Back\x20Up.mount
101ms user@1000.service
63ms systemd-udev-trigger.service
57ms systemd-sysusers.service
45ms tmp.mount
40ms systemd-journald.service
38ms polkit.service
35ms systemd-tmpfiles-setup.service
33ms systemd-udevd.service
32ms systemd-tmpfiles-setup-dev.service
31ms systemd-binfmt.service
30ms logrotate.service
27ms systemd-tmpfiles-clean.service
23ms ntpd.service
23ms alsa-restore.service
22ms kmod-static-nodes.service
22ms dev-hugepages.mount
21ms systemd-journal-catalog-update.service
20ms sys-kernel-config.mount
19ms systemd-update-utmp.service
17ms systemd-sysctl.service
15ms dev-mqueue.mount
14ms systemd-random-seed.service
7ms rtkit-daemon.service
7ms proc-sys-fs-binfmt_misc.mount
5ms sys-kernel-debug.mount
4ms systemd-user-sessions.service
3ms systemd-update-done.service


#3

Another way to post this, is with “systemd-analyze plot > boot.svg”. This will give you a graphical representation of your entire boot process.


#4

My VM boot time… Pending new mainline to fix AMD seg-fault issues.


#5

I’ll add this to the first post. Cool addition.


#6

It’s probably right in front of my face but what format option are you guys using for code blocks?


#7

I think the one @Dobbie03 was using is the quote feature though.

This is a block of code inside [code][/code] 

#8

Thanks AvnSgt

This result doesn’t surprise me…

glenn@desktop ~ % systemd-analyze
Startup finished in 4.159s (kernel) + 45.819s (userspace) = 49.978s
graphical.target reached after 12.460s in userspace

…and

glenn@desktop ~ % systemd-analyze blame
37.292s man-db.service
28.531s updatedb.service
5.913s lvm2-monitor.service
3.928s dev-sda2.device
2.419s NetworkManager.service
1.433s lightdm.service
1.098s accounts-daemon.service
952ms systemd-journal-flush.service
797ms systemd-tmpfiles-setup-dev.service
776ms polkit.service
616ms org.cups.cupsd.service
584ms ldconfig.service
479ms systemd-sysusers.service
408ms dev-disk-by\x2duuid-e5da94b0\x2dde54\x2d462a\x2d95e8\x2de1fa13e1e4ba.swap
341ms systemd-journal-catalog-update.service
320ms systemd-update-utmp.service
317ms systemd-udev-trigger.service
299ms user@1000.service
277ms sys-kernel-debug.mount
256ms kmod-static-nodes.service
243ms logrotate.service
lines 1-21

** Obviously I’m still not doing something right with formatting.


#9
 ~  systemd-analyze
Startup finished in 5.612s (kernel) + 5min 8.150s (userspace) = 5min 13.763s
graphical.target reached after 35.591s in userspace

~  systemd-analyze blame
    4min 55.327s updatedb.service
         37.144s man-db.service
         17.399s mpd.service
          8.757s systemd-journal-flush.service
          8.549s lvm2-monitor.service
          7.308s dev-sda3.device
          5.408s NetworkManager.service
          2.703s accounts-daemon.service
          1.804s systemd-udevd.service
          1.517s polkit.service
          1.135s systemd-logind.service
          1.131s systemd-tmpfiles-setup-dev.service
           979ms udisks2.service
           735ms wpa_supplicant.service
           660ms lightdm.service
           630ms upower.service
           625ms lm_sensors.service
           612ms systemd-modules-load.service
           598ms dev-hugepages.mount
           590ms logrotate.service
           578ms ntpd.service
           462ms systemd-remount-fs.service
           460ms dev-mqueue.mount
           459ms sys-kernel-debug.mount

#10

Read em and weep gents

Startup finished in 11.469s (firmware) + 6.062s (loader) + 1.242s (kernel) + 837ms (userspace) = 19.611s
graphical.target reached after 837ms in userspace

#11

:smile:


#12

I was using the block quote feature
block-quote.png


#13

Nice speeds, though at one point I was under 4 seconds. Not sure what has changed between then and now.


#15
[ettore@yoda-pc ~]$  systemd-analyze blame
          9.248s dev-sdb8.device
          8.836s lvm2-monitor.service
          6.023s ufw.service
          2.883s systemd-hwdb-update.service
          2.136s upower.service
          1.681s NetworkManager.service
          1.495s systemd-sysusers.service
          1.283s systemd-rfkill.service
          1.265s polkit.service
          1.162s ldconfig.service
          1.155s systemd-logind.service
          1.153s thermald.service
          1.150s alsa-restore.service
          1.103s org.cups.cupsd.service
          1.020s cpupower.service
           948ms rtkit-daemon.service
           883ms systemd-tmpfiles-setup-dev.service
           743ms tlp.service
           710ms systemd-modules-load.service
           700ms systemd-udevd.service
           565ms systemd-journald.service
           480ms systemd-journal-catalog-update.service
           454ms systemd-tmpfiles-setup.service
           415ms wpa_supplicant.service
           399ms systemd-update-utmp.service
           393ms udisks2.service
           356ms systemd-random-seed.service
           347ms systemd-udev-trigger.service
           338ms lightdm.service
           287ms user@1001.service
           222ms systemd-journal-flush.service
           216ms dev-mqueue.mount
           215ms sys-kernel-debug.mount
           215ms kmod-static-nodes.service
           210ms systemd-backlight@backlight:intel_backlight.service
           207ms systemd-fsck@dev-disk-by\x2duuid-9B0E\x2dCC36.service
           198ms tmp.mount
           198ms systemd-remount-fs.service
           197ms dev-hugepages.mount
           182ms systemd-sysctl.service
           113ms boot-efi.mount
           111ms systemd-tmpfiles-clean.service
            98ms ntpd.service
            64ms systemd-user-sessions.service
            25ms systemd-update-done.service
            23ms sys-kernel-config.mount
             4ms sys-fs-fuse-connections.mount
             3ms home-ettore-.cache.mount
lines 26-48/48 (END)

tomorrow place start ssd external
Best regards


#16

HDD
s/u finished in 3.149s (kernel) + 15.007s (userspace) = 18.156s
graphical.target reached after 15.006s in userspace
20180222 - - 3.341s + 11.331s = 14.672s and g.t=11.263s


#17

Impressive, are you on a SSD or HDD?


#18

Startup finished in 3.008s (kernel) + 20.211s (userspace) = 23.219s
graphical.target reached after 16.523s in userspace

      6.396s lvm2-monitor.service
      5.903s dev-sdb1.device
      3.405s lvm2-pvscan@8:19.service
      3.060s lvm2-pvscan@8:32.service
      2.922s NetworkManager.service
      2.886s systemd-journal-flush.service
      2.144s nfs-idmapd.service
      1.910s org.cups.cupsd.service
      1.904s systemd-modules-load.service
      1.737s gssproxy.service
      1.720s rpc-statd.service
      1.667s systemd-logind.service
      1.665s polkit.service
      1.443s systemd-udevd.service
      1.287s systemd-tmpfiles-setup-dev.service
      1.207s proc-fs-nfsd.mount
      1.075s nfs-mountd.service
       895ms nfs-server.service
       763ms user@1000.service
       612ms systemd-journald.service
       607ms systemd-udev-trigger.service
       580ms rtkit-daemon.service
       516ms rpcbind.service
       392ms systemd-user-sessions.service
       356ms ntpd.service
       266ms systemd-fsck@dev-disk-by\x2duuid-86ff8806\x2de1d7\x2d4e06\x2dbca3\x2da8e7b3732847.service
       245ms systemd-random-seed.service
       245ms systemd-update-utmp.service
       199ms systemd-remount-fs.service
       189ms kmod-static-nodes.service
       168ms dev-mqueue.mount
       161ms sys-kernel-debug.mount
       158ms systemd-sysctl.service
       143ms systemd-tmpfiles-setup.service
       105ms colord.service
        75ms dev-disk-by\x2duuid-d19bd553\x2db300\x2d4f65\x2daf7e\x2db459c0f58a58.swap
        73ms mnt-data.mount
        29ms rpc-statd-notify.service
        16ms dev-hugepages.mount
         9ms tmp.mount
         8ms sys-kernel-config.mount
         5ms var-lib-nfs-rpc_pipefs.mount

#19

ok, but if you do not post it is normal h.d. or ssd you do not understand much.


#20

my ssd estern samsung

bob@eva
 -------
 OS: ArchLabs x86_64
 Kernel: 4.8.14-1-ARCH
 Uptime: 29 secs
 Packages: 863
 Shell: zsh 5.4.2
 -------------------
 WM: Openbox
 Theme: ArchLabs-Dark
 Icons: ArchLabs-Light
 Terminal: terminator
 -----------
 CPU: Intel i7-3630QM @ 3.400GHz
 GPU: GeForce GT 635M
 GPU: Ivybridge Mobile
 Memory: 301MiB / 7877MiB
 
                          
 
bob@eva ~ % systemd-analyze blame
          1.576s lvm2-monitor.service
           997ms updatedb.service
           794ms man-db.service
           387ms systemd-logind.service
           264ms NetworkManager.service
           238ms dev-sda11.device
           231ms lightdm.service
            61ms accounts-daemon.service
            58ms logrotate.service
            57ms systemd-journal-flush.service
            52ms cpupower.service
            48ms polkit.service
            46ms user@1000.service
            45ms thermald.service
            43ms systemd-udevd.service
            41ms systemd-udev-trigger.service
            35ms systemd-journald.service
            34ms systemd-fsck@dev-disk-by\x2duuid-CBA0\x2d2BBE.service
            15ms systemd-tmpfiles-setup-dev.service
            14ms wpa_supplicant.service
            14ms systemd-remount-fs.service
            14ms boot-efi.mount
            13ms dev-mqueue.mount

130 bob@eva ~ %                                                              :(

#21
pitje@archmac ~ (git)-[master] % systemd-analyze
Startup finished in 23.076s (kernel) + 7.438s (userspace) = 30.515s
graphical.target reached after 3.107s in userspace
pitje@archmac ~ (git)-[master] % systemd-analyze blame
          4.090s man-db.service
          1.986s updatedb.service
           593ms dev-mapper-cryptroot.device
           442ms lvm2-monitor.service
           346ms lightdm.service
           274ms systemd-journal-flush.service
           252ms systemd-logind.service
           171ms NetworkManager.service
           166ms upower.service
           125ms ldconfig.service
           109ms systemd-fsck@dev-disk-by\x2duuid-811E\x2d7D19.service
            84ms systemd-rfkill.service
            68ms systemd-udev-trigger.service
            63ms systemd-journald.service
            53ms accounts-daemon.service
            43ms udisks2.service
            43ms boot.mount
            40ms polkit.service
            38ms systemd-sysusers.service
            33ms systemd-tmpfiles-setup-dev.service
            33ms systemd-udevd.service
            33ms bluetooth.service
            32ms geoclue.service
            26ms systemd-tmpfiles-setup.service
            25ms user@1000.service
            24ms systemd-binfmt.service
            21ms systemd-sysctl.service
            20ms logrotate.service
            19ms systemd-backlight@backlight:intel_backlight.service
            19ms dev-mqueue.mount
            18ms systemd-remount-fs.service
            17ms systemd-journal-catalog-update.service
            14ms dev-hugepages.mount
            14ms systemd-random-seed.service
            14ms systemd-tmpfiles-clean.service
            13ms systemd-modules-load.service
            11ms kmod-static-nodes.service
            10ms sys-kernel-debug.mount
            10ms wpa_supplicant.service
             8ms sys-fs-fuse-connections.mount