How long does systemd take for you? - Page 3

roelj · #31 15th March 2012, 05:26 PM

Code:

$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
  2093ms postgresql.service
   718ms udev-settle.service
   426ms udev-trigger.service
   214ms NetworkManager.service
   154ms ktune.service
   151ms lm_sensors.service
   150ms console-kit-log-system-start.service
   148ms systemd-tmpfiles-setup.service
   130ms iptables.service
   126ms ksm.service
   125ms fedora-loadmodules.service
   121ms systemd-readahead-replay.service
   114ms udev.service
   113ms jexec.service
   111ms mcelog.service
   109ms irqbalance.service
   108ms systemd-readahead-collect.service
   103ms fedora-storage-init-late.service
   103ms dbus.service
    95ms remount-rootfs.service
    95ms systemd-remount-api-vfs.service
    94ms systemd-sysctl.service
    93ms rc-local.service
    91ms fedora-storage-init.service
    90ms dev-mqueue.mount
    79ms systemd-user-sessions.service
    77ms fedora-readonly.service
    68ms systemd-vconsole-setup.service
    67ms media.mount
    58ms sys-kernel-debug.mount
    49ms sys-kernel-security.mount
    45ms fedora-wait-storage.service
    36ms dev-hugepages.mount
    30ms var-tmp-kdecache\x2droel.mount
    28ms console-kit-daemon.service
    24ms proc-sys-fs-binfmt_misc.mount
    24ms home.mount
    23ms tmp.mount                                                                                                                                                                  
    16ms ksmtuned.service                                                                                                                                                           
    16ms sys-kernel-config.mount                                                                                                                                                    
    14ms rtkit-daemon.service                                                                                                                                                       
     8ms systemd-logind.service                                                                                                                                                     
     8ms rpcbind.service

Code:

$ systemd-analyze time                                                                                                                                              
Startup finished in 2168ms (kernel) + 2553ms (initramfs) + 3238ms (userspace) = 7961ms

I have a Core2Duo 2.2Ghz, 4GB RAM and an SSD drive.

stevea · #32 15th March 2012, 06:53 PM

Quote:

Originally Posted by RupertPupkin

Interesting. After getting rid of several services (udev-settle.service, fedora-wait-storage.service, fedora-storage-init.service, fedora-storage-init-late.service, media.mount, dev-mqueue.mount) I was able to cut 4 seconds off my boot time:
...

Uhh - so what are the consequences of removing udevd-settle ? It seems that several other services that require hardware, like network services wait for ther.

My hunch is that there eis a chance for failure when the dependency is removed.

RupertPupkin · #33 15th March 2012, 07:48 PM

Quote:

Originally Posted by stevea

Uhh - so what are the consequences of removing udevd-settle ?

Uhh, none that I've seen. Everything still works on my machine, including networking. Maybe it's because I don't use NetworkManager, LVM or RAID. The article that kkshethin linked to explains it.

stevea · #34 15th March 2012, 08:06 PM

Tnx, I read Poettering's blog long ago (translates to "Request Concert, pony farm and adventure playground").

Yak - it looks like they need wrappers-around/re-writes-of LVM, RAID or Multipath instead of forcing the system to stall on udevd. It's pretty clear they need better high-level management tools. FWIW I'm seeing 'systemadm' crash pretty often on F16 (I need to bugzilla that).

I suppose it''s good that systemd exposes this problem.

PabloTwo · #35 23rd March 2012, 10:12 PM

Has anyone else noticed a "noticeable" increase in boot time after the update to the 3.3.0-4.fc16 kernel?
In post#2 on this thread back on Feb. 16, my results of Ruperts command line string ended with:

56 services: Total = 66.099 seconds

The same now gives me:

56 services: Total = 139.967 seconds

The "systemd-analyze time" command, before and after:

= 16898ms
= 45191ms

The obvious time suck: netfs.service. Again, the before and after times:

169ms netfs.service
21195ms netfs.service <== top of the list

This didn't happen after the last systemd update on Mar. 12, only after booting into new 3.3.0-4 kernel I installed yesterday. Anyone else?

Edit: I should add, I'm only experiencing this on my desktop pc with 3.3.0-4.fc16.x86_64, which has 3 internal sata hdd's, but not on my laptop running 3.3.0-4.fc16.i686 with a single hdd. In either case, no network shares or drives are being mounted. On the laptop, the ntefs.service blame time did rise to second from top, right under NetworkManager.service, but still a still reasonable 2941ms on an older and slower cpu, not enough that you notice any increased boot time like on the desktop pc.

***DBelton*** · #36 23rd March 2012, 10:36 PM

Something is wrong there.

Running the same kernel on my F16 machine here and sharing 10 drives through NFS, the netfs service is only taking 1413 ms according to systemd-analyze blame. (I can't shut it down right now to get the time running on the previous kernel, though)

Edit:

Just looked back and I had posted the times from this same machine on page 1

it had

545 ms for netfs.service

now I have

1413 ms for netfs.service

So, something did slow down

PabloTwo · #37 23rd March 2012, 10:58 PM

I'll boot the previous kernel and see happens there, though I expect I won't get that obvious boot up delay.

---------- Post added at 05:48 PM ---------- Previous post was at 05:41 PM ----------

Booting in the previous 3.2.10-3.fc16.x86_64 kernel there was no noticeable slowdown in the boot up time and running "systemd-analyze blame" gave me:

157ms netfs.service

And the "systemd-analyze time" gave me:

= 18640ms

It's a puzzle, eh?

---------- Post added at 05:58 PM ---------- Previous post was at 05:48 PM ----------

Now, on a "warm" reboot into the 3.3.0-4 kernel, boot time was closer to reasonable, though still a little more than that on the previous kernel. On this boot, the netfs.service came in at:

962ms netfs.service

..about the middle of the pack, and the systemd-analyze time gave me:

= 28727ms

Neither of these compare with the longer times doing a "cold" boot on the 3.3.0-4 kernel on the desktop PC.

Edit--Sun 24 March: Seems to be a hit or miss thing. On some cold boots netfs.service has a reasonable load time, but on some cold boots, it comes in at an outrageous time as I initially described. Boot up times on the 3.3.0-4 are longer across the board for almost all services compared to the previous kernels though.

stevea · #38 24th March 2012, 05:02 AM

Well - I've been able to pare-down the boot time on my laptop nicely,

Code:

[root@crucibulum Desktop]# systemd-analyze time
Startup finished in 1186ms (kernel) + 2048ms (initramfs) + 17626ms (userspace) = 20862ms

Code:

1029ms abrt-vmcore.service
   585ms netfs.service
   201ms systemd-binfmt.service
   140ms udev-trigger.service
   129ms remount-rootfs.service
   123ms NetworkManager.service
   121ms console-kit-log-system-start.service
   117ms systemd-remount-api-vfs.service
   117ms chronyd.service
   117ms home.mount
   113ms systemd-vconsole-setup.service
   110ms livesys.service
   108ms rsyslog.service
   107ms systemd-sysctl.service
   102ms lm_sensors.service
    97ms mcelog.service
    96ms ksm.service
    94ms fedora-loadmodules.service
    88ms systemd-logind.service
    82ms tcsd.service
    77ms irqbalance.service
    74ms sysstat.service
    72ms sshd-keygen.service
    69ms nfs-lock.service
    65ms systemd-readahead-collect.service
    64ms systemd-readahead-replay.service
    56ms abrt-ccpp.service
    55ms libvirtd.service
    53ms acpid.service
    51ms dbus.service
    47ms rc-local.service
    37ms media.mount
    37ms livesys-late.service
    35ms libvirt-guests.service
    35ms dev-mqueue.mount
    35ms xinetd.service
    33ms dev-hugepages.mount
    30ms sys-kernel-security.mount
    28ms fedora-readonly.service
    28ms sys-kernel-debug.mount
    27ms nfs-idmap.service
    21ms systemd-tmpfiles-setup.service
    20ms sandbox.service
    20ms var-lib-nfs-rpc_pipefs.mount
    19ms sys-kernel-config.mount
    15ms console-kit-daemon.service
    11ms rpcbind.service
    11ms ksmtuned.service
    10ms tmp.mount
     8ms systemd-user-sessions.service
     8ms proc-sys-fs-binfmt_misc.mount
     8ms udev.service
     7ms accounts-daemon.service
     3ms rtkit-daemon.service
54 services: Total = 4.845 seconds

But examining the plot ....

Code:

[root@crucibulum Desktop]# systemd-analyze plot > /tmp2/plot3.svg
[root@crucibulum Desktop]# eog /tmp2/plot3.svg

Showed two long delays in red. One was ~8 seconds for NetworkManager to attain a connection- sometimes less, rarely more. I guess that's acceptable.

The other is a mystery - was a ~8 seconds attributed to fsck of the /home directory. However this file system was tested clean and could be fsck'ed and mounted in far under 1 second. It's an SSD drive where root live - so no spinup or init delay.

So I modified /etc/fstab entry for /home from

Code:

-UUID=24941fe7-6d23-4969-951e-0872d4b81b0e /home		ext4	noatime,discard,data=writeback 1 2
+UUID=24941fe7-6d23-4969-951e-0872d4b81b0e /home		ext4	noatime,discard,data=writeback 1 0

After performing this, the 8 second red histo delay remained wbut was attributed to home.mount. Again this is nonsense - mount takes a tiny fraction of one second. So I hanged again to ...

Code:

+UUID=24941fe7-6d23-4969-951e-0872d4b81b0e /home		ext4	noatime,discard,data=writeback 0 0

and not the 8 second delay is not attributed to anything ... but the horrorific delay remains.

My ASSUMPTION is that I or the systemd-analyze tool is misinterpreting the issue.

#39 24th March 2012, 02:08 PM

Quote:

Originally Posted by stevea

Well - I've been able to pare-down the boot time on my laptop nicely,

Code:

[root@crucibulum Desktop]# systemd-analyze time
Startup finished in 1186ms (kernel) + 2048ms (initramfs) + 17626ms (userspace) = 20862ms

Code:

1029ms abrt-vmcore.service
   585ms netfs.service
   201ms systemd-binfmt.service
   140ms udev-trigger.service
   129ms remount-rootfs.service
   123ms NetworkManager.service
   121ms console-kit-log-system-start.service
   117ms systemd-remount-api-vfs.service
   117ms chronyd.service
   117ms home.mount
   113ms systemd-vconsole-setup.service
   110ms livesys.service
   108ms rsyslog.service
   107ms systemd-sysctl.service
   102ms lm_sensors.service
    97ms mcelog.service
    96ms ksm.service
    94ms fedora-loadmodules.service
    88ms systemd-logind.service
    82ms tcsd.service
    77ms irqbalance.service
    74ms sysstat.service
    72ms sshd-keygen.service
    69ms nfs-lock.service
    65ms systemd-readahead-collect.service
    64ms systemd-readahead-replay.service
    56ms abrt-ccpp.service
    55ms libvirtd.service
    53ms acpid.service
    51ms dbus.service
    47ms rc-local.service
    37ms media.mount
    37ms livesys-late.service
    35ms libvirt-guests.service
    35ms dev-mqueue.mount
    35ms xinetd.service
    33ms dev-hugepages.mount
    30ms sys-kernel-security.mount
    28ms fedora-readonly.service
    28ms sys-kernel-debug.mount
    27ms nfs-idmap.service
    21ms systemd-tmpfiles-setup.service
    20ms sandbox.service
    20ms var-lib-nfs-rpc_pipefs.mount
    19ms sys-kernel-config.mount
    15ms console-kit-daemon.service
    11ms rpcbind.service
    11ms ksmtuned.service
    10ms tmp.mount
     8ms systemd-user-sessions.service
     8ms proc-sys-fs-binfmt_misc.mount
     8ms udev.service
     7ms accounts-daemon.service
     3ms rtkit-daemon.service
54 services: Total = 4.845 seconds

But examining the plot ....

Code:

[root@crucibulum Desktop]# systemd-analyze plot > /tmp2/plot3.svg
[root@crucibulum Desktop]# eog /tmp2/plot3.svg

Showed two long delays in red. One was ~8 seconds for NetworkManager to attain a connection- sometimes less, rarely more. I guess that's acceptable.

The other is a mystery - was a ~8 seconds attributed to fsck of the /home directory. However this file system was tested clean and could be fsck'ed and mounted in far under 1 second. It's an SSD drive where root live - so no spinup or init delay.

So I modified /etc/fstab entry for /home from

Code:

-UUID=24941fe7-6d23-4969-951e-0872d4b81b0e /home		ext4	noatime,discard,data=writeback 1 2
+UUID=24941fe7-6d23-4969-951e-0872d4b81b0e /home		ext4	noatime,discard,data=writeback 1 0

After performing this, the 8 second red histo delay remained wbut was attributed to home.mount. Again this is nonsense - mount takes a tiny fraction of one second. So I hanged again to ...

Code:

+UUID=24941fe7-6d23-4969-951e-0872d4b81b0e /home		ext4	noatime,discard,data=writeback 0 0

and not the 8 second delay is not attributed to anything ... but the horrorific delay remains.

My ASSUMPTION is that I or the systemd-analyze tool is misinterpreting the issue.

Thanks for the fsck tip

Code:

$ systemd-analyze time
Startup finished in 2998ms (kernel) + 2460ms (initramfs) + 4444ms (userspace) = 9903ms

Uploaded with ImageShack.us

Cygn · #40 3rd April 2012, 11:26 AM

Hi folks,

I've got something strange with initramfs:

Code:

$ systemd-analyze time
Startup finished in 1431ms (kernel) + 10579ms (initramfs) + 3084ms (userspace) = 15095ms

My / is on a SSD, hence the lovely 3s userspace but I'm surprised that the initramfs takes up to 10 s ?? /boot is separate on a seagate barracuda, so I don't think that it's the HD read speed issue...

Any ideas ?

sea · #41 3rd April 2012, 09:47 PM

My netbook reports:

Code:

systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}' && systemd-analyze 
  4490ms NetworkManager.service
  1401ms systemd-vconsole-setup.service
  1117ms mcelog.service
   892ms abrt-vmcore.service
   790ms remount-rootfs.service
   735ms fedora-readonly.service
   694ms media.mount
   641ms udev-trigger.service
   622ms auditd.service
   621ms nfs-lock.service
   576ms abrt-ccpp.service
   565ms gpm.service
   523ms sys-kernel-config.mount
   517ms dbus.service
   506ms udev.service
   451ms irqbalance.service
   395ms rtkit-daemon.service
   359ms systemd-user-sessions.service
   347ms rpcbind.service
   193ms systemd-remount-api-vfs.service
   178ms home.mount
   147ms systemd-readahead-collect.service
   109ms systemd-sysctl.service
   102ms console-kit-daemon.service
     1ms sys-fs-fuse-connections.mount
25 services: Total = 16.972 seconds
Startup finished in 2179ms (kernel) + 5320ms (initramfs) + 14670ms (userspace) = 22170ms

After these 2 values differ, i'm now going to do a real time measure.

EDIT:
3 cold reboots later, the values are more mathing, allthough not to the 'right' direction...

Code:

systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}' && systemd-analyze 
  4458ms NetworkManager.service
  2180ms irqbalance.service
  1486ms fedora-readonly.service
  1429ms abrt-ccpp.service
  1404ms systemd-vconsole-setup.service
  1072ms mcelog.service
   892ms nfs-lock.service
   718ms media.mount
   709ms gpm.service
   661ms remount-rootfs.service
   652ms dbus.service
   579ms systemd-user-sessions.service
   541ms sys-kernel-config.mount
   492ms auditd.service
   445ms udev-trigger.service
   427ms udev.service
   276ms abrt-vmcore.service
   266ms rpcbind.service
   208ms systemd-remount-api-vfs.service
   159ms systemd-readahead-collect.service
   130ms rtkit-daemon.service
   114ms home.mount
    97ms systemd-sysctl.service
    93ms console-kit-daemon.service
     1ms sys-fs-fuse-connections.mount
25 services: Total = 19.489 seconds
Startup finished in 2190ms (kernel) + 4844ms (initramfs) + 13528ms (userspace) = 20563ms

kosh · #42 13th May 2012, 11:58 PM

My good old IBM X60s

Code:

$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
 27360ms remount-rootfs.service
 20981ms systemd-vconsole-setup.service
 20912ms udev-settle.service
 14499ms fedora-loadmodules.service
  8444ms media.mount
  8438ms sys-kernel-debug.mount
  8433ms dev-mqueue.mount
  8426ms sys-kernel-security.mount
  8419ms dev-hugepages.mount
  8411ms udev-trigger.service
  6728ms udev.service
  6377ms systemd-remount-api-vfs.service
  2925ms systemd-sysctl.service
  1700ms sys-kernel-config.mount
   379ms NetworkManager.service
   315ms bluetooth.service
   223ms rsyslog.service
   208ms fedora-storage-init.service
   204ms systemd-logind.service
   201ms systemd-readahead-collect.service
   195ms systemd-readahead-replay.service
   188ms systemd-tmpfiles-setup.service
   169ms console-kit-log-system-start.service
   160ms sandbox.service
   156ms iptables.service
   154ms chronyd.service
   137ms auditd.service
   130ms mcelog.service
   129ms sshd-keygen.service
   123ms acpid.service
   107ms dbus.service
   106ms irqbalance.service
    92ms systemd-user-sessions.service
    56ms fedora-storage-init-late.service
    51ms fedora-readonly.service
    48ms console-kit-daemon.service
    46ms boot.mount
    33ms fedora-wait-storage.service
38 services: Total = 155.663 seconds

Code:

$ systemd-analyze time
Startup finished in 2565ms (kernel) + 4961ms (initramfs) + 32821ms (userspace) = 40348ms

DrHappyAngry · #43 2nd June 2012, 06:38 PM

I managed to get my time down quite a lot. For some reason I was getting a lot of link reset failed messages during kernel startup with 40gb intel sata2 SSD plugged into one of the sata3 ports on my asus P8P67 deluxe mobo. Moving the drive to a sata2 port on the mobo stopped those and greatly decreased the kernel startup time. Autofs seems to be handled a lot better in fc17 for my nfs mounts, as well.

I also followed a lot of the tips here http://www.harald-hoyer.de/personal/...5-to-3-seconds Be very careful with some of the advice there, you can easily hose up your system if you don't know what you're doing. Disabling the initrd really cuts down the boot time, but you do have to switch from mounting by uuids to old school device nodes in the grub config and fstab. You also have to be very careful when upgrading the kernel. I really should read up more on grub2 in order to get these options automatically set correctly during a kernel upgrade.

So this is 40gb sata2 intel ssd, P8P67 deluxe, i7 2600k.

Code:

 systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
   526ms NetworkManager.service
   491ms postfix.service
   447ms plymouth-start.service
   427ms avahi-daemon.service
   396ms systemd-logind.service
   364ms lm_sensors.service
   333ms console-kit-log-system-start.service
   332ms dbus.service
   327ms mcelog.service
   324ms ip6tables.service
   319ms iptables.service
   313ms livesys.service
   313ms systemd-binfmt.service
   309ms auditd.service
   308ms ksm.service
   287ms irqbalance.service
   271ms gpm.service
   242ms systemd-user-sessions.service
   214ms udev-trigger.service
   170ms fedora-loadmodules.service
   162ms systemd-readahead-collect.service
   146ms systemd-readahead-replay.service
   139ms fedora-readonly.service
   134ms sys-kernel-config.mount
   125ms mdmonitor-takeover.service
   123ms systemd-vconsole-setup.service
   123ms media.mount
   121ms systemd-sysctl.service
   100ms sshd.service
    96ms dev-mqueue.mount
    95ms rpcbind.service
    80ms dev-hugepages.mount
    75ms autofs.service
    73ms nfs-lock.service
    66ms sys-kernel-debug.mount
    61ms scratch.mount
    56ms systemd-remount-fs.service
    40ms proc-sys-fs-binfmt_misc.mount
    31ms livesys-late.service
    30ms systemd-tmpfiles-setup.service
    29ms ksmtuned.service
    28ms colord-sane.service
    28ms udisks2.service
    25ms tmp.mount
    17ms boot.mount
    15ms udev.service
    12ms colord.service
    12ms console-kit-daemon.service
     5ms upower.service
     4ms accounts-daemon.service
     1ms sys-fs-fuse-connections.mount
     1ms rtkit-daemon.service
52 services: Total = 8.766 seconds

Code:

systemd-analyze time
Startup finished in 1014ms (kernel) + 11635ms (userspace) = 12650ms

chepioq · #44 2nd June 2012, 06:47 PM

Code:

[dominique@host ~]$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
   664ms fedora-storage-init.service
   408ms udev-settle.service
   387ms akmods.service
   247ms NetworkManager.service
   182ms lm_sensors.service
   180ms systemd-logind.service
   157ms avahi-daemon.service
   143ms rsyslog.service
   142ms systemd-binfmt.service
   140ms auditd.service
   121ms mcelog.service
   117ms acpid.service
   111ms irqbalance.service
    93ms gpm.service
    92ms dbus.service
    91ms systemd-readahead-collect.service
    85ms udev-trigger.service
    78ms systemd-readahead-replay.service
    78ms systemd-tmpfiles-setup.service
    75ms systemd-user-sessions.service
    74ms fedora-readonly.service
    74ms home.mount
    70ms boot.mount
    65ms systemd-vconsole-setup.service
    63ms media.mount
    61ms systemd-remount-fs.service
    59ms fedora-loadmodules.service
    54ms sys-kernel-debug.mount
    49ms systemd-sysctl.service
    47ms udisks2.service
    45ms dev-mqueue.mount
    23ms rc-local.service
    23ms fedora-wait-storage.service
    20ms dev-hugepages.mount
    20ms fedora-storage-init-late.service
    18ms sys-kernel-config.mount
    17ms proc-sys-fs-binfmt_misc.mount
    15ms udev.service
     6ms upower.service
     4ms rtkit-daemon.service
     1ms sys-fs-fuse-connections.mount
41 services: Total = 4.399 seconds

Code:

[dominique@host ~]$ systemd-analyze time
Startup finished in 1311ms (kernel) + 1349ms (initramfs) + 6108ms (userspace) = 8769ms
[dominique@host ~]$

With Fedora17 Beefy Miracle, and ssd OCZ Vextex2.

TK492 · #45 6th June 2012, 04:53 AM

From an up-to-date F17 on a 3 year old 2.8GHz Core2Duo laptop:

Code:

[jeremy@XPS ~]$ systemd-analyze blame|awk '{print $0;sum=sum+$1} END {print NR,"services: Total =",sum/1000,"seconds"}'
  5788ms fedora-storage-init.service
  2325ms udev-settle.service
  1881ms systemd-remount-fs.service
  1018ms udev.service
   953ms udev-trigger.service
   915ms fedora-loadmodules.service
   876ms fedora-wait-storage.service
   864ms media.mount
   836ms dev-hugepages.mount
   830ms dev-mqueue.mount
   822ms sys-kernel-debug.mount
   794ms NetworkManager.service
   742ms colord-sane.service
   678ms fedora-storage-init-late.service
   606ms systemd-vconsole-setup.service
   551ms sys-kernel-config.mount
   514ms fedora-readonly.service
   460ms vboxdrv.service
   350ms boot.mount
   349ms mdmonitor-takeover.service
   335ms rsyslog.service
   330ms systemd-readahead-collect.service
   304ms systemd-logind.service
   298ms systemd-user-sessions.service
   294ms colord.service
   291ms lm_sensors.service
   286ms avahi-daemon.service
   286ms home.mount
   279ms chronyd.service
   206ms rc-local.service
   188ms dbus.service
   180ms systemd-tmpfiles-setup.service
   178ms livesys.service
   175ms iptables.service
   175ms ip6tables.service
   171ms auditd.service
   159ms mcelog.service
   147ms abrt-vmcore.service
   139ms bluetooth.service
   136ms abrt-ccpp.service
   131ms irqbalance.service
   110ms systemd-readahead-replay.service
    68ms upower.service
    55ms lvm2-monitor.service
    54ms dkms_autoinstaller.service
    54ms jexec.service
    40ms udisks2.service
    37ms systemd-sysctl.service
    21ms spice-vdagentd.service
    21ms vboxballoonctrl-service.service
    19ms vboxweb-service.service
    17ms accounts-daemon.service
    15ms livesys-late.service
     6ms rtkit-daemon.service
     3ms proc-sys-fs-binfmt_misc.mount
     2ms sys-fs-fuse-connections.mount
56 services: Total = 27.362 seconds

Code:

[jeremy@XPS ~]$ systemd-analyze time
Startup finished in 1289ms (kernel) + 4384ms (initramfs) + 107982ms (userspace) = 113657ms

I'll read related articles that have been posted earlier and see if I can improve!

UPDATE:

I effected the following changes

Quote:

ln -s /dev/null /etc/systemd/system/udev-settle.service
ln -s /dev/null /etc/systemd/system/fedora-wait-storage.service
ln -s /dev/null /etc/systemd/system/fedora-storage-init.service
ln -s /dev/null /etc/systemd/system/fedora-storage-init-late.service

And my services take around 4 seconds less to start and my startup is done in 114962ms (weird that it is actually higher?)

.