Il 06/11/2017 12:33, Marco Calistri ha scritto:
Il 06/11/2017 11:22, Anton Aylward ha scritto:
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!
I've saved an html and a SVG output plot, I will review as soon as possible
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
I don't remember now my result of the above command...I will run it again and compare with your.
Cheers,
-- Marco Calistri
Before closing down my office I had the luck to find this interesting article: https://lizards.opensuse.org/2012/07/26/optimizing-a-boot-time-aka-2-second-... I would ask here to more experts people: how in practice we can "Mask" a service to prevent it being started by systemd? (citing a brief part by the author of the article): *Making a laptop boot twice more faster* *So having the complex dependencies of several services in mind, I decided to mask some of them. Masking in systemd world means the service cannot be started using systemd, so it becomes invisible for it. I masked those* Very curious to try same approach used above on my Tumbleweed :-) Cheers, -- Marco Calistri -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org