Faster boot?

Hey, guys. Any ideas on how I can speed boot time?


Startup finished in 2.557s (kernel) + 2.305s (initrd) + 20.944s (userspace) = 25.806s
          9.821s NetworkManager.service
          9.133s display-manager.service
          8.395s polkit.service
          2.489s \x2esnapshots.mount
          2.410s var-tmp.mount
          1.601s var-spool.mount
          1.474s lvm2-activation.service
          1.424s var-opt.mount
          1.263s lvm2-activation-early.service
          1.023s var-log.mount
           969ms var-lib-pgsql.mount
           942ms systemd-udev-settle.service
           902ms var-lib-named.mount
           846ms var-lib-mailman.mount
           806ms systemd-udev-root-symlink.service
           802ms sys-kernel-debug.mount
           798ms dev-hugepages.mount
           797ms dev-mqueue.mount
           759ms alsa-restore.service
           754ms systemd-user-sessions.service
           735ms var-crash.mount
           733ms usr-local.mount
           721ms tmp.mount
           674ms systemd-tmpfiles-setup-dev.service
           669ms home.mount
           625ms srv.mount
           507ms systemd-logind.service
           499ms wpa_supplicant.service
           499ms rc-local.service
           488ms systemd-udev-trigger.service
           485ms systemd-backlight@backlight:acpi_video0.service
           476ms dm-event.service
           474ms opt.mount
           456ms systemd-tmpfiles-setup.service
           445ms systemd-remount-fs.service
           442ms ModemManager.service
           335ms systemd-update-utmp.service
           333ms boot-grub2-x86_64\x2defi.mount
           252ms systemd-fsck@dev-disk-by\x2duuid-9a7c1e27\x2d4372\x2d4bca\x2d8e88\x2d01d9b0857625.service
           205ms udisks2.service
           189ms dev-disk-by\x2duuid-e1e0147b\x2d6ab5\x2d4f67\x2d81b4\x2ddf1b8269aaa6.swap
           181ms cycle.service
           172ms systemd-rfkill@rfkill1.service
           167ms systemd-rfkill@rfkill2.service
           126ms user@1000.service
           118ms systemd-sysctl.service
           105ms systemd-random-seed.service
            96ms systemd-modules-load.service
            74ms systemd-rfkill@rfkill0.service
            73ms upower.service
            58ms systemd-readahead-replay.service
            37ms rtkit-daemon.service
            28ms boot-grub2-i386\x2dpc.mount
            18ms plymouth-start.service
            15ms iscsi.service
            12ms systemd-vconsole-setup.service
            10ms systemd-readahead-collect.service
             9ms systemd-update-utmp-runlevel.service
             7ms kmod-static-nodes.service
             7ms systemd-udevd.service
             7ms systemd-journal-flush.service
             6ms sys-fs-fuse-connections.mount
             5ms systemd-readahead-done.service
             4ms systemd-rfkill@rfkill3.service
             2ms systemd-backlight@backlight:radeon_bl0.service

http://cdn4.wccftech.com/wp-content/uploads/2014/02/Intel-SSD-730-Series-Box.jpg

Hahahaha yeah, thats beyond my money.

Apart from that ( :slight_smile: ) maybe using Wicked instead of NetworkManager might help.

I currently have about 7 seconds boot time on SSD with Wicked. I have very modest needs and no WLAN on this workstation so…

I have never used Wicked, but I will check it. On my 13.1, I had about 14 sec boot time with Network manager. I don’t know why this has been slowed in 13.2. Also, there are some services that I have disabled but still get ran. For example, lvm2.

Wicked has replaced ifup in 13.2

That’s strange. I just upgraded from 13.1 to 13.2 and am now booting much faster, on xfce.

25 seconds isn’t fast enough for you? Maybe you should have been around to see the boot times in the late 1980s, and compare them. Or, even Windows boot times late 1990s/early 2000s.:wink:

You would likely not complain, if you compare those against the 25 seconds.

What would you do with the extra 11 seconds that is productive, if you could shave that off?:\

It takes me longer than 11 seconds to put the batteries in the wireless keyboard and wireless mouse while booting.:slight_smile:

Can you post your wicked-config file please?
If I use wicked it waits 34 seconds on boot until the network comes up. If I switch to NetworkManager it needs 6 seconds. That is on an Tumbleweed with SSD. On another system wicked works fine and fast also with tumble. so it must be some config stuff I think. I already tried turning off ipv6 but no change…

On 2014-12-21 22:46, tomtomme wrote:

> If I use wicked it waits 34 seconds on boot until the network comes up.
> If I switch to NetworkManager it needs 6 seconds. That is on an
> Tumbleweed with SSD. On another system wicked works fine and fast also
> with tumble. so it must be some config stuff I think. I already tried
> turning off ipv6 but no change…

dhcp?


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Hi,

You can use the mask option for that lvm2 service.

systemctl mask blahblah.service

yes dhcp - on all my systems. So if this is the cause - why is networkmanager so much faster?
Can I turn off the behaviour, that the systems waits for the connection on boot?

On 2014-12-23 11:26, tomtomme wrote:

> yes dhcp - on all my systems. So if this is the cause - why is
> networkmanager so much faster?

I don’t know if it is the cause of your problem, but there are at least
two different dhcp client daemons, and on some networks one of them can
be slow for some reason and the other fast. So the trick is switch to
the “other”, whatever that be.

In nm the setting is in /etc/NetworkManager/NetworkManager.conf

dhcp
This key sets up what DHCP client NetworkManager will use.
Presently dhclient and dhcpcd are supported. The client configured
here should be available on your system too. If this key is
missing, available DHCP clients are looked for in this order:
dhclient, dhcpcd.

In wicked I have no idea.

> Can I turn off the behaviour, that the systems waits for the connection
> on boot?

Unsure. By definition, a system connection has to be up before network
related services go up, so they have to wait.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

interesting. thanks.
In fact I have two systems with tumbleweed on the same router / network here. One is fast with wicked, the other with nm. Very weird. And even more weird, seldomly ALSO the otherwise working solution is slow (like 30 seconds, checked with systemd-analyze blame).
However - everything worked fine before 13.2 was released (old Tumbleweed)… so I am not convinced on what is really going on… even if your idea of the root problem seems logic to mee.

thanks again. I think I will live with it for now…