On 06/11/17 07:07 AM, Arjen de Korte wrote:
So now I would like to ask: why SuSEfirewall2_init.service, display-manager.service, NetworkManager.service, took so long time to be up and running at least on my system?
I don't know if there is a way to check this, but I highly suspect these services are waiting for disk-I/O. All caches are empty at boot time, so everything has to come from disk. This is where SSD drives with essentially zero seek times shine. Changing to SSD drives has been the single biggest performance improvement on my systems.
The first thing that Marco needs to understand is the dependency chain. That's why Carlos pointed to "critical-chain". Ff course that's not the full chain. The critical chain is a one-dimensional slice of the start-up order, which is actually a lot in parallel. To see it all, you need to use the "plot" option. OH MY! The second thing is that yes, there is kernel time, but there is also time in userspace those apps spend initializing, chundling the results of reading those table and caches. # systemd-analyze time Startup finished in 4.103s (kernel) + 4.227s (initrd) + 32.196s (userspace) = 40.526s -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org