After going through the thread Speeding Up Linux I came to know that booting speed can be tweaked and my system is insanely slow.
Just after booting up (KDE loaded, after entering username and password), I got following output in konsole
akash@akash:~> systemd-analyze critical-chain
Bootup is not yet finished. Please try again later.
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
Only after sometime the konsole gave the output it should.
akash@akash:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @8min 16.381s
└─multi-user.target @8min 16.381s
└─dkms.service @20.128s +2min 13.215s
└─basic.target @20.119s
└─timers.target @20.118s
└─systemd-tmpfiles-clean.timer @20.118s
└─sysinit.target @20.118s
└─apparmor.service @19.827s +290ms
└─systemd-tmpfiles-setup.service @19.304s +522ms
└─local-fs.target @19.291s
└─run-user-1000-gvfs.mount @1min 3.794s
└─local-fs-pre.target @6.435s
└─systemd-remount-fs.service @6.268s +165ms
└─systemd-fsck-root.service @5.197s +1.069s
└─systemd-readahead-replay.service @4.851s +222ms
└─system.slice
└─-.slice
Why is my system taking so much time. My hardware is not that old.
My system - Acer V3 571G Laptop, Core i5 - 3230M with 4GB DD3, Nvidia 710M GPU with bumblebee installed and 750 GB HDD
So what my laptop has HDD not SSD. 8min 29.588sec booting time is insane. >:(
Yesterday I happened to talk to sysrich on irc and I clearly envy his system which boots up in 5 secs straight.
Those two should only show up on the first boot after a kernel update. And kernel updates are infrequent (maybe once every three months), unless you are getting them from the kernel repo.
On 2015-04-23 15:46, vish 99 wrote:
>
> robin_listas;2706437 Wrote:
>> On 2015-04-23 12:46, vish 99 wrote:
>>
>>> 7min 56.247s purge-kernels.service
>>> 2min 13.215s dkms.service
>
> Yes and how can I decrease it?
You probably can’t. However, that should only happen once, just after
you updated the kernel. You might have a look at the logs to find out
the sequence of events.
akash@akash:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @51.511s
└─multi-user.target @51.511s
└─cron.service @51.511s
└─postfix.service @51.169s +341ms
└─network.target @51.151s
└─NetworkManager.service @50.884s +266ms
└─SuSEfirewall2_init.service @18.074s +32.808s
└─basic.target @17.654s
└─timers.target @17.653s
└─systemd-tmpfiles-clean.timer @17.653s
└─sysinit.target @17.653s
└─apparmor.service @17.301s +351ms
└─systemd-tmpfiles-setup.service @16.543s +756ms
└─local-fs.target @16.530s
└─run-media-akash-DATA.mount @12.713s +2.454s
└─dev-disk-by\x2dlabel-DATA.device @12.712s
Q1. Can I put a limit that ModemManager.service should look to connect for only certain period of time and after that it should quit searching for internet whether it connects to internet or not.
Q2. What is the shortest method to turn on / turn off the ModemManager.service? Will it take less than 13.859s? I know it’s insane question.
Hi
The blame is only an indicator, I would guess the culpret is dkms service and probably related to vbox service, something is probably being rebuilt and/or failing.
If you disable the vbox service temporarily, is there an improvement?
Nope. Instead it increases the booting time. Time for dkms.service increases to 22.993s from 13.353s. So, I’m re-enabling vboxdrv.service
akash@akash:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @42.310s
└─multi-user.target @42.310s
└─SuSEfirewall2.service @30.292s +12.016s
└─network.target @30.243s
└─NetworkManager.service @28.276s +1.964s
└─SuSEfirewall2_init.service @19.523s +8.746s
└─basic.target @18.743s
└─timers.target @18.742s
└─systemd-tmpfiles-clean.timer @18.742s
└─sysinit.target @18.742s
└─apparmor.service @17.897s +845ms
└─systemd-tmpfiles-setup.service @17.655s +240ms
└─local-fs.target @17.640s
└─run-media-akash-DATA.mount @12.963s +3.077s
└─dev-disk-by\x2dlabel-DATA.device @12.962s
akash@akash:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @36.644s
└─multi-user.target @36.644s
└─cron.service @36.644s
└─postfix.service @35.774s +868ms
└─network.target @35.755s
└─NetworkManager.service @35.516s +238ms
└─SuSEfirewall2_init.service @18.823s +16.691s
└─basic.target @18.058s
└─timers.target @18.058s
└─systemd-tmpfiles-clean.timer @18.058s
└─sysinit.target @18.058s
└─apparmor.service @17.772s +285ms
└─systemd-tmpfiles-setup.service @17.424s +347ms
└─local-fs.target @17.413s
└─run-media-akash-DATA.mount @11.772s +2.523s
└─dev-disk-by\x2dlabel-DATA.device @11.771s
If you disable networking when you do not need it, and turn off the firewall before shutting down, then turn your firewall back on after booting, it will make a significant difference to your boot time.
You might also look into the long display-manager.service time. But, keep in mind, neither it nor ModemManager.service are in the critical chain.
You can lessen the initrd load time from almost 4 seconds to a couple seconds less by disabling or removing Plymouth and running:
mkinitrd
But, your biggest boot-time improvement is going to come from booting with the firewall disabled.
You could investigate further to see why your firewall takes so long to load, and I think that may be affected by the ModemManager.service with a similar time.
ModemManager.service on my Acer Laptop (core 2 duo 2Ghz, 2-Gig memory) is 396ms compared to your 32 seconds + 266ms time.
Firewall on mine is 7.383 seconds compared to almost 33 seconds on yours.
