when startup delays become bugs

Jeffrey Bastian jbastian at redhat.com
Tue May 14 22:56:38 UTC 2013

On Tue, May 14, 2013 at 03:51:44PM -0600, Chris Murphy wrote:
> But firewalld goes from 7 seconds to 18 seconds? Why? avahi-daemon,
> restorecond, all are an order of magnitude longer on F19 than F18.

And it was even faster on F17.  I had F17 cold booting to a usable
Xfce desktop in 3.6 seconds by following Harald Hoyer's guide [1]:
  Startup finished in 1470ms (kernel) + 2130ms (userspace) = 3601ms

But F18 and F19 now take 16 seconds on the same system:
  Startup finished in 1.061s (kernel) + 15.299s (userspace) = 16.361s

The slowest component on F19 is this new "wait" service:
         10.102s NetworkManager-wait-online.service

This service doesn't seem to do anything other than wait until the
network is fully up.  This really skews unfavorably the boot time
reported by systemd-analyze.  But if I mask that service and reboot,
everthing still appears to work fine and systemd-analyze reports a boot
time of only 6.2 seconds.

I wonder if there are other oddities like this that are skewing the
statistics reported by systemd-analyze.


[1] http://www.harald-hoyer.de/personal/blog/fedora-17-boot-optimization-from-15-to-3-seconds

More information about the devel mailing list