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


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bootup time
#1
So I was at Costco and decided to try Linux Lite 5.0 to see if everything worked (wifi being the most important)
I picked an HP, I-7, with nvdia  graphics card, 16 gig of memory and a 512 gig of ss storage to boot up LL 5.0 from my USB.
It took just as long to boot up as my old laptop at home!! I was surprised to think that a new hot machine would not make it boot in a flash.
Does anyone have comments on why it takes LL so long to boot on old or new??
Reply
#2
[member=6213]Abw[/member]  Running from USB even if USB3.0 will be slower than a harddrive..


Boot time could be a number of things from something loading or waiting (app) or to something faulty...


Could try.... the below to see whats taking the longest....
Code:
systemd-analyze
systemd-analyze blame
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz  - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express  -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
Reply
#3
OK!Thanks for the reply and the command. Here's the output and please tell me it the numbers look out of the ordinary.. This is an older Dell Vostro 2420 w/ 4 gig memory and an I-3...



andrew  ~  systemd-analyze blame
        17.943s systemd-journal-flush.service
        17.061s motd-news.service
        16.607s ufw.service
        15.148s dev-sda1.device
        12.723s lvm2-monitor.service
        12.384s systemd-tmpfiles-setup-dev.service
        11.853s systemd-modules-load.service
        11.729s keyboard-setup.service
          7.099s NetworkManager-wait-online.service
          6.526s nmbd.service
          4.382s networkd-dispatcher.service
          3.092s vboxdrv.service
          2.610s gpu-manager.service
          2.574s NetworkManager.service
          2.438s grub-common.service
          2.438s systemd-random-seed.service
          2.294s plymouth-quit-wait.service
          2.241s udisks2.service
          2.187s lightdm.service
          2.062s accounts-daemon.service
          1.833s preload.service
          1.784s swapfile.swap
          1.326s resolvconf-pull-resolved.service
          1.177s wpa_supplicant.service
          975ms tlp.service
          865ms upower.service
          717ms ModemManager.service
          660ms console-kit-daemon.service
          646ms blk-availability.service
          637ms binfmt-support.service
          618ms systemd-udev-trigger.service
          608ms smbd.service
          534ms systemd-journald.service
          514ms systemd-tmpfiles-setup.service
          510ms teamviewerd.service
          490ms bluetooth.service
          476ms avahi-daemon.service
          473ms proc-sys-fs-binfmt_misc.mount
          467ms rsyslog.service
          447ms networking.service
          432ms thermald.service
          429ms colord.service
          422ms apparmor.service
          395ms systemd-remount-fs.service
          374ms console-kit-log-system-start.service
          278ms lm-sensors.service
          244ms dev-hugepages.mount
          243ms sys-kernel-debug.mount
          241ms dev-mqueue.mount
          226ms kmod-static-nodes.service
          225ms systemd-logind.service
          217ms systemd-sysctl.service
          157ms systemd-timesyncd.service
          151ms systemd-tmpfiles-clean.service
          147ms [email protected]
          145ms systemd-resolved.service
          125ms setvtrgb.service
          107ms polkit.service
            95ms apport.service
            88ms systemd-udevd.service
            77ms plymouth-read-write.service
            76ms plymouth-start.service
            38ms alsa-restore.service
            32ms systemd-update-utmp.service
            26ms pppd-dns.service
            24ms ubiquity.service
            18ms hddtemp.service
            17ms console-setup.service
            15ms dns-clean.service
            12ms resolvconf.service
            7ms systemd-update-utmp-runlevel.service
            7ms ureadahead-stop.service
            6ms systemd-backlight@backlight:intel_backlight.service
            6ms vboxweb-service.service
            6ms systemd-user-sessions.service
            5ms sys-fs-fuse-connections.mount
            4ms finalrd.service
            4ms vboxballoonctrl-service.service
            4ms rtkit-daemon.service
            4ms vboxautostart-service.service
            3ms sys-kernel-config.mount
            3ms openvpn.service
AND



andrew  ~  systemd-analyze
Startup finished in 5.270s (kernel) + 41.256s (userspace) = 46.526s
graphical.target reached after 40.280s in userspace

Reply
#4
Code:
systemd-analyze critical-chain

will point out time frames between steps. Other than that, your boot up looks fine, any hindrance would be hardware selection. You could also set a static ip address to speed things up.
Reply
#5
Mine also is the same problem! On my netbook with 2gb ram, LL 4.8 took only 28 seconds to boot up, and after installing LL 5.0, it is taking more than 2 minutes time to boot and get to display of desktop!! The update or upgrade should refine and iron out any glitches in the older version but should not make it a horror to bear!!
Perhaps I am thinking to roll back to 4.8 now, leaving this ghostly upgrade!!
Kpnrao
Reply
#6
systemd-analyze
systemd-analyze blame
Welcome to Linux Lite 5.0 kpnrao

Monday 22 June 2020, 13:55:52
Memory Usage: 595/1975MB (30.13%)
Disk Usage: 8/228GB (4%)
Support - https://www.freecinema2022.gq/forums/ (Right click, Open Link)

kpnrao  ~  systemd-analyze
Startup finished in 8.043s (kernel) + 1min 20.059s (userspace) = 1min 28.102s
graphical.target reached after 1min 16.879s in userspace
kpnrao  ~  systemd-analyze blame
27.106s networking.service                                 
16.504s blueman-mechanism.service                           
13.278s NetworkManager-wait-online.service                 
13.016s systemd-udev-settle.service                         
12.781s networkd-dispatcher.service                         
11.091s accounts-daemon.service                             
10.912s dev-sda5.device                                     
10.909s udisks2.service                                     
9.512s polkit.service                                     
7.926s avahi-daemon.service                               
7.879s bluetooth.service                                   
7.137s firewalld.service                                   
5.885s thermald.service                                   
5.863s systemd-logind.service                             
5.828s wpa_supplicant.service                             
5.781s grub-common.service                                 
4.948s smartmontools.service                               
4.788s systemd-resolved.service                           
4.325s smbd.service                                       
4.023s systemd-networkd.service                           
3.929s upower.service                                     
3.712s nmbd.service                                       
3.698s systemd-journald.service
************************
above is the systemd analyze report....
Please guide me to get out of the horrible 2.43 min boot time of LL 5.0 machine!!
Kpnrao
Reply
#7
Rolled back from the snail like 5.0 to a bit fast booting LL 4.8! the systemd-analyze blame is here!!
kpnrao  ~  systemd-analyze
Startup finished in 8.723s (kernel) + 40.340s (userspace) = 49.063s
graphical.target reached after 40.303s in userspace
kpnrao  ~  systemd-analyze blame
        19.760s dev-sda1.device
        12.928s ufw.service
        12.609s lvm2-monitor.service
        12.128s systemd-modules-load.service
        12.092s systemd-tmpfiles-setup-dev.service
        11.547s swapfile.swap
        10.914s systemd-journal-flush.service
          8.018s NetworkManager-wait-online.service
          6.579s NetworkManager.service
          6.524s networkd-dispatcher.service
          6.466s udisks2.service
          4.311s nmbd.service
          3.838s ModemManager.service
          3.795s keyboard-setup.service
          3.626s thermald.service
          3.512s accounts-daemon.service
          2.738s systemd-random-seed.service
          2.415s systemd-journald.service
          2.223s grub-common.service
          1.614s avahi-daemon.service
          1.377s systemd-tmpfiles-clean.service
          1.321s smbd.service
          1.082s polkit.service
*****************************
Where is the difference for the slowness in LL 5.0 after all?? May please be addressed in upcoming upgrades!!
Kpnrao
Reply
#8
(06-19-2020, 03:30 AM)Abw link Wrote:OK!Thanks for the reply and the command. Here's the output and please tell me it the numbers look out of the ordinary.. This is an older Dell Vostro 2420 w/ 4 gig memory and an I-3...



andrew  ~  systemd-analyze blame
        17.943s systemd-journal-flush.service
        17.061s motd-news.service
        16.607s ufw.service
        15.148s dev-sda1.device
        12.723s lvm2-monitor.service
        12.384s systemd-tmpfiles-setup-dev.service
        11.853s systemd-modules-load.service
        11.729s keyboard-setup.service
          7.099s NetworkManager-wait-online.service
          6.526s nmbd.service
          4.382s networkd-dispatcher.service
          3.092s vboxdrv.service
          2.610s gpu-manager.service
          2.574s NetworkManager.service
          2.438s grub-common.service
          2.438s systemd-random-seed.service
          2.294s plymouth-quit-wait.service
          2.241s udisks2.service
          2.187s lightdm.service
          2.062s accounts-daemon.service
          1.833s preload.service
          1.784s swapfile.swap
          1.326s resolvconf-pull-resolved.service
          1.177s wpa_supplicant.service
          975ms tlp.service
         
AND

andrew  ~  systemd-analyze
Startup finished in 5.270s (kernel) + 41.256s (userspace) = 46.526s
graphical.target reached after 40.280s in userspace

If you have an HDD, 46.256s is still on the slow boot time. I would have masked some services like ufw, lvm2,nmbd, ModemManager, etc ... because I don't use them. I would also have a workaround on journal flush.

If you have an SSD, boot time would be around 8-15sec. I used to have around 8sec on LL 4.8. Now I'm having 11sec on LL5.
Reply
#9
I have a Computer I picked up at CostCo 2 years ago (HP Pavilion 590-p0057c, upgraded to 32 Gig) last week I pulled out the existing drive and installed a WD Black 6TB Performance Internal Hard Drive - 7200 RPM along with a Sabrent 1TB Rocket NVMe PCIe M.2 2280 Internal SSD. 

I also installed a 500 Gig SSD drive on a four year old Toshiba laptop and boosted it's memory to 16 gig.

On both PC's I installed Linux Lite 5.0, the only difference is on the HP Desktop I installed ROOT to the M.2 drive and set HOME to the 6TB drive.

The laptop is at the main screen in less than 30 seconds.  The Desktop takes about 2 minutes. 

Now, the Desktop also has a Startech USB 3.0 → HDMI interface (USB32HD4K) for a second monitor but the boot time was not this long when it was running Linux Mint 19.
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)