I was curious to see how much total time systemd takes to start all the services, since my boot times in Fedora with systemd are about 10-12 seconds longer than with the old SysV init system. So I looked at the
systemd-analyze blame command and used awk to add up the times. Of course systemd starts services in parallel, so the sum of the individual times is far greater than the actual time it takes to boot (given by the
systemd-analyze time command). But I thought it was interesting to see nonetheless. Here are the commands I ran:
Code:
systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
systemd-analyze time
and here's the output:
Code:
$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
16117ms remount-rootfs.service
12878ms systemd-vconsole-setup.service
10940ms media.mount
10854ms sys-kernel-debug.mount
10815ms dev-mqueue.mount
10023ms systemd-remount-api-vfs.service
8669ms fedora-storage-init.service
5769ms udev-settle.service
4109ms udev-trigger.service
4088ms udev.service
2861ms network.service
2270ms fedora-wait-storage.service
1979ms dkms_autoinstaller.service
1744ms systemd-sysctl.service
915ms console-kit-log-system-start.service
742ms gpm.service
672ms rsyslog.service
552ms lm_sensors.service
535ms systemd-readahead-collect.service
534ms systemd-readahead-replay.service
388ms fedora-storage-init-late.service
360ms gnustep.service
268ms sendmail.service
211ms fedora-readonly.service
175ms systemd-logind.service
160ms systemd-user-sessions.service
140ms dbus.service
126ms boot.mount
108ms xfs.service
74ms rc-local.service
59ms sm-client.service
46ms systemd-tmpfiles-setup.service
26ms vsftpd.service
18ms xinetd.service
34 services: Total = 109.225 seconds
$ systemd-analyze time
Startup finished in 1836ms (kernel) + 3633ms (initramfs) + 28530ms (userspace) = 34000ms
So it took 34 seconds to boot, despite all 34 services taking about 109 seconds.
Post your output here!
Threaded Mode
