Choose style:

Author Topic: system Bootup time [Solved]  (Read 1025 times)

0 Members and 1 Guest are viewing this topic.

Offline Ly

  • Member
  • ***
  • Posts: 201
  • Karma: 24
  • New Forum User
    • View Profile
system Bootup time [Solved]
« on: August 25, 2017, 06:57:29 am »
I just started my computer and here is the system bootup time :
Code: [Select]
systemd-analyze
Startup finished in 5.705s (kernel) + 1min 49.080s (userspace) = 1min 54.786s
which is far superior to my normal bootup time (which is around 30-37 secs)

the only thing i did recently was to tinker around with Eclipse and installing the latest version of Python (3.6.2).

Code: [Select]
systemd-analyze blame
    1min 17.397s apt-daily.service
         13.898s dev-sda5.device
          9.720s systemd-udevd.service
          7.561s NetworkManager-wait-online.service
          5.349s apt-daily-upgrade.service
          4.027s mintsystem.service
          3.666s apparmor.service
          3.484s grub-common.service
          3.417s irqbalance.service
          3.326s and.service
          3.313s networking.service
          3.310s ondemand.service
          3.274s lightdm.service
          2.288s ModemManager.service
          2.246s upower.service
          2.001s accounts-daemon.service
          1.832s NetworkManager.service
          1.749s nmbd.service
          1.567s samba-ad-dc.service
          1.395s keyboard-setup.service
          1.296s thermald.service
          1.136s systemd-tmpfiles-setup-dev.service
          1.108s systemd-modules-load.service
it seems the "apt daily service" is taking too much, any clue ?
« Last Edit: August 25, 2017, 08:33:21 am by Ly »

Offline VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5597
  • Karma: 1012
  • Peppermint Mod
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: system Bootup time
« Reply #1 on: August 25, 2017, 07:23:04 am »
Hrm ... I'm fully updated.  Here's mine, for comparison:

Code: [Select]
╭─vindsl@Boogaloo-5 ~  
╰─➤  systemd-analyze
Startup finished in 1.386s (kernel) + 6.685s (userspace) = 8.072s
╭─vindsl@Boogaloo-5 ~ 
╰─➤  systemd-analyze blame
          5.123s apt-daily.service
           700ms dev-sda5.device
           584ms psad.service
           521ms postfix.service
           441ms nmbd.service
           402ms samba-ad-dc.service
           363ms systemd-fsck@dev-disk-by\x2duuid-621A\x2dD074.service
           350ms mintsystem.service
           208ms wicd.service
           206ms console-setup.service
           191ms smbd.service
           166ms ufw.service
           120ms accounts-daemon.service
           115ms nvidia-persistenced.service
           109ms plymouth-read-write.service
           105ms networking.service
           105ms ModemManager.service
            96ms systemd-update-utmp.service
            77ms grub-common.service
            69ms irqbalance.service
            58ms sensord.service
            51ms pppd-dns.service
            51ms gpu-manager.service
            50ms rsyslog.service
            50ms systemd-user-sessions.service
            48ms keyboard-setup.service
            44ms plymouth-start.service
            43ms systemd-logind.service
            43ms systemd-udev-trigger.service
            43ms lightdm.service
            42ms systemd-journald.service
            40ms thermald.service
            39ms udisks2.service
            39ms avahi-daemon.service
            37ms upower.service
            34ms systemd-tmpfiles-setup-dev.service
            33ms systemd-udevd.service
            31ms systemd-modules-load.service
            29ms colord.service
            28ms ondemand.service
            26ms home.mount
            22ms systemd-fsck@dev-disk-by\x2duuid-c88aa6d7\x2d5773\x2d4ea8\x2d9b
            22ms dev-sda7.swap
            21ms dev-sda10.swap
            18ms hddtemp.service
            18ms polkitd.service
            17ms apparmor.service
            16ms dev-mqueue.mount
            15ms sys-kernel-debug.mount
            15ms user@1000.service
            13ms snapd.autoimport.service
            12ms dev-hugepages.mount
            12ms alsa-restore.service
          5.123s apt-daily.service
           700ms dev-sda5.device
           584ms psad.service
           521ms postfix.service
           441ms nmbd.service
           402ms samba-ad-dc.service
           363ms systemd-fsck@dev-disk-by\x2duuid-621A\x2dD074.service
           350ms mintsystem.service
           208ms wicd.service
           206ms console-setup.service
           191ms smbd.service
           166ms ufw.service
           120ms accounts-daemon.service
           115ms nvidia-persistenced.service
           109ms plymouth-read-write.service
           105ms networking.service
           105ms ModemManager.service
            96ms systemd-update-utmp.service
            77ms grub-common.service
            69ms irqbalance.service
            58ms sensord.service
            51ms pppd-dns.service
            51ms gpu-manager.service

[1]  + 24909 suspended  systemd-analyze blame
╭─vindsl@Boogaloo-5 ~ 
╰─➤  systemd-analyze critical-chain                                       148 ↵
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 @2.149s
└─multi-user.target @2.149s
  └─smbd.service @1.958s +191ms
    └─nmbd.service @1.515s +441ms
      └─network-online.target @1.515s
        └─network.target @1.515s
          └─networking.service @1.409s +105ms
            └─network-pre.target @1.280s
              └─resolvconf.service @1.276s +3ms
                └─system.slice @82ms
                  └─-.slice @73ms
╭─vindsl@Boogaloo-5 ~ 
╰─➤
I'd install 'Bootchart' and see if that gives a visual clue of what's going on in your userspace.  ;)

EDIT

BTW...

Code: [Select]
╭─vindsl@Boogaloo-5 ~  
╰─➤  uname -svr
Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017
« Last Edit: August 25, 2017, 07:41:31 am by VinDSL, Reason: Addendum »

Offline Ly

  • Member
  • ***
  • Posts: 201
  • Karma: 24
  • New Forum User
    • View Profile
Re: system Bootup time
« Reply #2 on: August 25, 2017, 07:40:13 am »
it wasn't even the full command output :( ( 8 Secs Vin what the hell ? give me your secret!  :o )
systemd-analyze
Code: [Select]
systemd-analyze blame
    1min 17.397s apt-daily.service
         13.898s dev-sda5.device
          9.720s systemd-udevd.service
          7.561s NetworkManager-wait-online.service
          5.349s apt-daily-upgrade.service
          4.027s mintsystem.service
          3.666s apparmor.service
          3.484s grub-common.service
          3.417s irqbalance.service
          3.326s and.service
          3.313s networking.service
          3.310s ondemand.service
          3.274s lightdm.service
          2.288s ModemManager.service
          2.246s upower.service
          2.001s accounts-daemon.service
          1.832s NetworkManager.service
          1.749s nmbd.service
          1.567s samba-ad-dc.service
          1.395s keyboard-setup.service
          1.296s thermald.service
          1.136s systemd-tmpfiles-setup-dev.service
          1.108s systemd-modules-load.service
           927ms run-rpc_pipefs.mount
           917ms systemd-journald.service
           795ms ufw.service
           734ms avahi-daemon.service
           634ms systemd-tmpfiles-setup.service
           566ms dev-mqueue.mount
           550ms sys-kernel-debug.mount
           520ms dev-hugepages.mount
           482ms systemd-journal-flush.service
           424ms lm-sensors.service
           395ms systemd-sysctl.service
           330ms dev-disk-by\x2duuid-8f9b8819\x2de763\x2d4569\x2d856c\x2dfd2edb1d5
           324ms polkitd.service
           276ms kmod-static-nodes.service
           244ms console-kit-daemon.service
           220ms console-setup.service
           211ms alsa-restore.service
           193ms smbd.service
           193ms systemd-udev-trigger.service
           158ms plymouth-start.service
           149ms plymouth-read-write.service
           126ms gpu-manager.service
           124ms udisks2.service
           124ms console-kit-log-system-start.service
           114ms systemd-rfkill.service
           107ms rsyslog.service
           101ms binfmt-support.service
            97ms systemd-remount-fs.service
            85ms ntp.service
            57ms wpa_supplicant.service
            42ms systemd-random-seed.service
            40ms setvtrgb.service
            36ms systemd-logind.service
            32ms systemd-tmpfiles-clean.service
            28ms systemd-update-utmp.service
            19ms pppd-dns.service
            18ms user@1000.service
            14ms hddtemp.service
            11ms dns-clean.service
             7ms nfs-config.service
             7ms systemd-user-sessions.service
             6ms resolvconf.service
             4ms rc-local.service
             4ms proc-sys-fs-binfmt_misc.mount
             3ms systemd-update-utmp-runlevel.service
             3ms ureadahead-stop.service
             3ms rtkit-daemon.service
             3ms bluetooth.service
             2ms plymouth-quit-wait.service
             2ms sys-fs-fuse-connections.mount
             1ms systemd-backlight@backlight:intel_backlight.service

and
Code: [Select]
uname -svr
Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017

i just don't know what could cause this since i didn't add any application with my system startup.

EDIT :
i just restarted my computer (i didn't do anything at all !) and here is the new bootup time :
Code: [Select]
systemd-analyze
Startup finished in 5.475s (kernel) + 27.629s (userspace) = 33.105s
which is what i usually get
i give up on trying to figure out what went wrong.
Thanks for the help anyway Vin (8s start up time ? plz teach me your ways master ! xD )
« Last Edit: August 25, 2017, 07:53:16 am by Ly »

Offline spence

  • Administrator
  • Veteran
  • *****
  • Posts: 2237
  • Karma: 250
  • peppermint user since 2010
    • View Profile
    • My MeWe profile
  • Peppermint version(s): Peppermint 10
Re: system Bootup time [Solved]
« Reply #3 on: December 01, 2017, 02:34:08 pm »
Yes Mr Dizzle... @Ly and I both need your peppermintZen wizardry in mastering this boot wisdom   :-\

Code: [Select]
spence@antec ~ $ systemd-analyze
Startup finished in 6.659s (kernel) + 18.993s (userspace) = 25.652s
spence@antec ~ $ systemd-analyze blame
          8.836s NetworkManager-wait-online.service
          6.194s apt-daily.service
          3.784s rtkit-daemon.service
          2.073s apt-daily-upgrade.service
          1.620s apparmor.service
           325ms plymouth-read-write.service
           130ms dev-nvme0n1p2.device
           126ms plymouth-start.service
           113ms systemd-modules-load.service
            81ms mintsystem.service
            59ms accounts-daemon.service
            58ms networking.service
            57ms ModemManager.service
            46ms lightdm.service
            41ms console-setup.service
            39ms systemd-udev-trigger.service
            39ms udisks2.service
            34ms and.service
            32ms irqbalance.service
            32ms NetworkManager.service
            30ms systemd-logind.service
            29ms grub-common.service
            29ms ondemand.service
            27ms packagekit.service
            25ms upower.service
lines 1-25
spence
PeppermintOS 10 Respin currently installed  on:
'16 Antec Aria rebuild
 '18 Asus VivoBook


Do not despair, grasshopper...
    with patience all will be revealed...
       Through pain, enlightenment will come.