LINUX LITE 7.2 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What must I do with the systemd-analyze critical chain informations
#3
Hello Moltke,

Understood the informations coming from systemd-analyze time.
Done your advices

=> cmd systemd-analyze blame

1min 30.243s nmbd.service
        57.570s resolvconf-pull-resolved.service
        28.391s systemd-journal-flush.service
        27.938s dev-sda1.device
        24.810s mysql.service
        19.786s keyboard-setup.service
        17.993s ufw.service
        16.123s lvm2-monitor.service
        16.070s snapd.service
        15.289s systemd-modules-load.service
        15.232s systemd-tmpfiles-setup-dev.service
        14.623s [email protected]
        11.954s NetworkManager.service
        11.368s udisks2.service
        10.065s ModemManager.service
        10.027s NetworkManager-wait-online.service
          9.007s apparmor.service
          6.220s accounts-daemon.service
          4.621s networking.service
          4.454s console-kit-log-system-start.service
          4.393s lmt-poll.service
          4.379s rsyslog.service
          4.353s networkd-dispatcher.service
          4.241s grub-common.service
          3.478s lightdm.service
          3.472s plymouth-quit-wait.service

So results are faster boot. 

I now note than
- "vboxadd.service" has disappeared, as expected
- "plymouth-quit-wait.service" now takes 3.5 sec compared with 1min26...
- "nmbd.service" is now the longuest process with 1min 30sec...


Now, shutdown the computer and restart again...

Results are :

=> cmd sudo systemd-analyze time

Startup finished in 37.363s (kernel) + 1min 22.578s (userspace) = 1min 59.942s
graphical.target reached after 1min 22.505s in userspace

=> cmd sudo systemd-analyze blame

        42.724s resolvconf-pull-resolved.service
        32.790s mysql.service
        28.599s dev-sda1.device
        28.486s systemd-journal-flush.service
        20.695s snapd.service
        18.441s keyboard-setup.service
        17.515s ufw.service
        15.258s lvm2-monitor.service
        15.034s systemd-tmpfiles-setup-dev.service
        14.522s systemd-modules-load.service
        10.506s NetworkManager.service
          9.950s [email protected]
          8.839s ModemManager.service
          7.541s accounts-daemon.service
          7.013s apparmor.service
          5.669s smbd.service
          5.495s NetworkManager-wait-online.service
          5.437s rsyslog.service
          5.325s udisks2.service
          5.109s nmbd.service
          4.890s devolonetsvc.service
          4.681s systemd-resolved.service
          4.426s apport.service



See also : https://askubuntu.com/questions/1247213/...down-my-ub

and then : https://doc.ubuntu-fr.org/snap
specially the 5. and 6.


i.e with an other computer, i5-6200U @ 2.3GHz, same LL4.8 : kernel 4.259sec and userspace 40.5 sec...
Same order process : vboxadd.service 34 sec and plymouth-quit-wait.service for 33 sec then 6sec and less for all the others process...

Thanks

Laurent
Reply


Messages In This Thread
Re: What must I do with the systemd-analyze critical chain informations - by lolo75 - 10-20-2020, 02:40 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)