[SOLVED]Help improving boot time

jmboris · 2014-12-08 15:56:54

Hi !

I want to improve my boot time but I dont know whay multi-user.target always is reached at 1:30 sec aprox.
I changed from gnome to XFCE and time is ver similar.
My machine :

SSD Kingston
CPU: AMD Athlon II X2 270 @ 3.4GHz
GPU: GeForce GTX 560 Ti
RAM: 1200MB / 3957MB

systemd-analyze
Startup finished in 2.282s (kernel) + 1min 30.114s (userspace) = 1min 32.396s

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 30.113s
└─multi-user.target @1min 30.113s
  └─systemd-journal-upload.service @1.783s
    └─network.target @1.781s
      └─wicd.service @1.320s +460ms
        └─basic.target @1.313s
          └─timers.target @1.313s
            └─shadow.timer @1.313s
              └─time-sync.target @1.312s
                └─systemd-timesyncd.service @1.296s +12ms
                  └─systemd-tmpfiles-setup.service @1.285s +10ms
                    └─local-fs.target @1.284s
                      └─run-user-1000-gvfs.mount @10.448s
                        └─run-user-1000.mount @9.712s
                          └─local-fs-pre.target @205ms
                            └─systemd-tmpfiles-setup-dev.service @164ms +41ms
                              └─kmod-static-nodes.service @128ms +10ms
                                └─system.slice @104ms
                                  └─-.slice @104ms

systemd-analyze blame
           606ms systemd-fsck@dev-sdb3.service
           460ms wicd.service
           435ms lvm2-monitor.service
           340ms mnt-disco1.mount
           195ms systemd-fsck@dev-sdb1.service
           152ms udisks2.service
           136ms systemd-logind.service
           134ms systemd-journald.service
           124ms lm_sensors.service
           123ms upower.service
           123ms avahi-daemon.service
           120ms netctl.service
           120ms ip6tables.service
           119ms alsa-restore.service
           118ms healthd.service
           118ms dhcpcd.service
           113ms iptables.service
           107ms wpa_supplicant.service
           100ms mnt-disco2.mount
            95ms systemd-vconsole-setup.service
            60ms polkit.service
            58ms systemd-sysctl.service
            57ms systemd-udevd.service
lines 1-23...skipping...
           606ms systemd-fsck@dev-sdb3.service
           460ms wicd.service
           435ms lvm2-monitor.service
           340ms mnt-disco1.mount
           195ms systemd-fsck@dev-sdb1.service
           152ms udisks2.service
           136ms systemd-logind.service
           134ms systemd-journald.service
           124ms lm_sensors.service
           123ms upower.service
           123ms avahi-daemon.service
           120ms netctl.service
           120ms ip6tables.service
           119ms alsa-restore.service
           118ms healthd.service
           118ms dhcpcd.service
           113ms iptables.service
           107ms wpa_supplicant.service
           100ms mnt-disco2.mount
            95ms systemd-vconsole-setup.service
            60ms polkit.service
            58ms systemd-sysctl.service
            57ms systemd-udevd.service
            46ms systemd-journal-flush.service
            44ms systemd-binfmt.service
            41ms systemd-tmpfiles-setup-dev.service
            31ms systemd-tmpfiles-clean.service
            28ms systemd-remount-fs.service
            27ms systemd-udev-trigger.service
            24ms dev-hugepages.mount
            24ms dev-mqueue.mount
            24ms sys-kernel-debug.mount
            23ms blk-availability.service
            20ms sys-kernel-config.mount
            17ms systemd-networkd.service
            16ms user@1000.service
            14ms systemd-random-seed.service
            12ms systemd-timesyncd.service
            12ms systemd-user-sessions.service
            11ms systemd-resolved.service
            10ms kmod-static-nodes.service
            10ms systemd-tmpfiles-setup.service
            10ms systemd-rfkill@rfkill1.service
             9ms systemd-rfkill@rfkill0.service
             7ms var-log.mount
             6ms proc-sys-fs-binfmt_misc.mount
             6ms var-tmp.mount
             4ms systemd-update-utmp.service
             4ms rtkit-daemon.service
             1ms tmp.mount

plot:

http://i.imgur.com/8PIPxDO.png

thanks

Last edited by jmboris (2014-12-16 18:47:19)

Head_on_a_Stick · 2014-12-08 16:11:50

I have noticed this when using netctl -- the active desktop is reached fairly quickly but the output of `systemd-analyze` is not available until a minute or so later and displays a similarly tardy time.

Have you tried manually timing how long it takes to get to an active desktop?

According to the plot, the last service (udisks2) is finished just after 13 seconds.

Trilby · 2014-12-08 16:14:58

Is there any clock syncing service running that might be adjusting the system time during boot (such as ntpd, or now systemd also can do this I think). If so, could your hardware clock be a minute or so behind?

jmboris · 2014-12-08 16:32:07

thanks for replays ..

manually i get my login screen @ 6 seconds and after login my desktop @ 13 seconds...... thats is ok for me but system-analyze makes me angry !!!!!

I dont have a ntp service

EDIT:

i made a test with netcl disabled and the results are very similar

Last edited by jmboris (2014-12-08 16:49:57)

jmboris · 2014-12-16 18:46:21

hi !!!!!

SOLVED

systemd-analyze
Startup finished in 2.206s (kernel) + 1.577s (userspace) = 3.783s

I was trying to solve my problem , so I searched in the systemd folders for something that looks "strange" in my multi-usert.target becuase I noticed that always the time was 1 min 30 sec to reach multi-user.target and I found to symbolik links ( wpa_supplican services ) broken ....

the two symlinks brokes was here :

/etc/systemd/system/multi-user.target.wants

so

sudo systemctl disbale wpa_supplicantXXXXXXX . service 

sudo systemctl disbale wpa_supplicantYYYYYYYYY. service 

sudo reboot

Then i got :

systemd-analyze
Startup finished in 2.206s (kernel) + 1.577s (userspace) = 3.783s

yeah !!!!!!!

Arch Linux

#1 2014-12-08 15:56:54

[SOLVED]Help improving boot time

#2 2014-12-08 16:11:50

Re: [SOLVED]Help improving boot time

#3 2014-12-08 16:14:58

Re: [SOLVED]Help improving boot time

#4 2014-12-08 16:32:07

Re: [SOLVED]Help improving boot time

#5 2014-12-16 18:46:21

Re: [SOLVED]Help improving boot time

Board footer