Arch Linux

davidjosepha

Member

Registered: 2013-02-21

Posts: 54

[SOLVED] Boot time calculation

I've been trying to speed up my boot and have a question about the calculation for boot time. When I run

systemd-analyze

I get the result

Startup finished in 3.563s (kernel) + 1min 31.568s (userspace) = 1min 35.132s

However, when I run

systemd-analyze blame

it returns a list of startup processes that sum to less than 11 seconds to complete. I know the full boot time includes the time it takes for everything to get completely ready, and that the OS may be usable before boot is complete, but where are those extra 80 seconds coming from?

Edit: Here's some more info

systemd-analyze blame
          1.118s postgresql.service
           417ms httpd.service
           324ms alsa-restore.service
           112ms ip6tables.service
           100ms dhcpcd@enp5s0.service
            89ms lm_sensors.service
            76ms systemd-logind.service
            66ms systemd-fsck@dev-disk-by\x2duuid-e6437955\x2d0f4f\x2d4649\x2dbc42\x2dd4c58515ce95.service
            63ms iptables.service
            63ms dhcpcd.service
            60ms systemd-binfmt.service
            59ms systemd-vconsole-setup.service
            54ms systemd-remount-fs.service
            54ms systemd-udev-trigger.service
            53ms mnt-video.mount
            44ms mnt-other.mount
            39ms mnt-audio.mount
            23ms tmp.mount
            20ms systemd-journal-flush.service
            18ms sys-kernel-debug.mount
            18ms sys-kernel-config.mount
            17ms systemd-tmpfiles-setup.service
            17ms systemd-tmpfiles-setup-dev.service
            16ms dev-mqueue.mount
            15ms user@1000.service
            14ms dev-hugepages.mount
            12ms kmod-static-nodes.service
             9ms systemd-sysctl.service
             7ms proc-sys-fs-binfmt_misc.mount
             5ms home.mount
             4ms systemd-update-utmp.service
             4ms systemd-user-sessions.service
             3ms systemd-udevd.service
             3ms systemd-random-seed.service

systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 31.510s
└─multi-user.target @1min 31.510s
  └─[1;31mpostgresql.service @1min 30.392s +1.118s[0m
    └─network.target @1min 30.389s
      └─[1;31mdhcpcd.service @822ms +63ms[0m
        └─basic.target @744ms
          └─timers.target @717ms
            └─man-db.timer @690ms
              └─sysinit.target @558ms
                └─[1;31msystemd-update-utmp.service @552ms +4ms[0m
                  └─[1;31msystemd-tmpfiles-setup.service @533ms +17ms[0m
                    └─local-fs.target @531ms
                      └─[1;31mhome.mount @525ms +5ms[0m
                        └─[1;31msystemd-fsck@dev-disk-by\x2duuid-e6437955\x2d0f4f\x2d4649\x2dbc42\x2dd4c58515ce95.service @456ms +66ms[0m
                          └─dev-disk-by\x2duuid-e6437955\x2d0f4f\x2d4649\x2dbc42\x2dd4c58515ce95.device @452ms

It looks like there's a huge amount of time completing network.target but I'm not sure why...

Edit: Looks like the issue was a static network configuration it was trying to set up, but that failed after 90 seconds, allowing network.target to complete. I just did

netctl disable network

to get it working

Last edited by davidjosepha (2014-08-22 22:39:38)