Linux Lite 4.0

[bermudalite]

systemd-analyze blame
        31.763s lightdm.service
        31.754s plymouth-quit-wait.service
        10.906s dev-sda1.device
        10.889s systemd-journal-flush.service
          9.671s ufw.service
          8.934s lvm2-monitor.service
          8.237s systemd-tmpfiles-setup-dev.service
          6.581s systemd-sysctl.service
          6.460s NetworkManager-wait-online.service
          4.556s NetworkManager.service
          4.196s keyboard-setup.service
          4.082s udisks2.service
          3.821s grub-common.service
          3.567s ModemManager.service
          2.407s accounts-daemon.service
          2.320s thermald.service
          2.305s networkd-dispatcher.service
          2.138s systemd-modules-load.service
          2.018s hddtemp.service
          1.554s polkit.service
          1.371s [email protected]
          1.193s apport.service
          1.186s avahi-daemon.service
lines 1-23...skipping...
        31.763s lightdm.service
        31.754s plymouth-quit-wait.service
        10.906s dev-sda1.device
        10.889s systemd-journal-flush.service
          9.671s ufw.service
          8.934s lvm2-monitor.service
          8.237s systemd-tmpfiles-setup-dev.service
          6.581s systemd-sysctl.service
          6.460s NetworkManager-wait-online.service
          4.556s NetworkManager.service
          4.196s keyboard-setup.service
          4.082s udisks2.service
          3.821s grub-common.service
          3.567s ModemManager.service
          2.407s accounts-daemon.service
          2.320s thermald.service
          2.305s networkd-dispatcher.service
          2.138s systemd-modules-load.service
          2.018s hddtemp.service
          1.554s polkit.service
          1.371s [email protected]
          1.193s apport.service
          1.186s avahi-daemon.service
          1.168s iio-sensor-proxy.service
          1.161s bluetooth.service
          1.143s alsa-restore.service
          1.142s console-kit-log-system-start.service
          1.142s ubiquity.service
          1.127s pppd-dns.service
          1.120s rsyslog.service
          1.116s gpu-manager.service
          932ms motd-news.service
          775ms upower.service
          645ms dev-mqueue.mount
          614ms systemd-remount-fs.service
          587ms dev-hugepages.mount


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 @53.003s
└─lightdm.service @21.239s +31.763s
  └─systemd-user-sessions.service @21.229s +7ms
    └─network.target @21.226s
      └─NetworkManager.service @16.667s +4.556s
        └─dbus.service @15.675s
          └─basic.target @15.627s
            └─sockets.target @15.627s
              └─acpid.socket @15.626s
                └─sysinit.target @15.527s
                  └─systemd-timesyncd.service @15.207s +320ms
                    └─systemd-tmpfiles-setup.service @15.002s +177ms
                      └─systemd-journal-flush.service @4.111s +10.889s
                        └─systemd-remount-fs.service @3.493s +614ms
                          └─systemd-journald.socket @3.425s
                            └─system.slice @3.424s
                              └─-.slice @3.057s

[Valtam]

[member=7174]bermudalite[/member] looks like your HDD (age) could be the culprit here. Would be interesting to see what your boot time would be with a modern SSD.

[bermudalite]

I figured as much.  Guess it might be time to retire the old boy.  :'(

[Valtam]

I would pick up a cheap SSD, it's a great laptop upgrade choice.

[coltman151]

First post! I just upgraded my 8 year old Acer Aspire to an older Intel SSD. Rather than cloning the old drive, I went to add LL to the new one and realized 4.0 was released. I'm in love with the flat theme, and all the new icons. Anyhow, I seen the discussion of boot times and thought I'd chime in with mine. I'll try to list all the tweaks I did, in case anyone is interested.

-Changed scheduler to Noop
-added noatime to the root partition

I rebooted, and came up with a 23 second boot time. Not bad. However, I ran systemd-analyze and found out that 7 seconds was waiting on the Networkmanager-wait-online service, and 5 seconds was waiting on Samba. I disabled the wait online service, and uninstalled samba (I have no windows computers, anywhere). You can see from the attachment, LL 4.0 is capable of some pretty good boot times even on old, cheap hardware.

EDIT: My attachment didn't show up, but here's the output of systemd-analyze

Code:

systemd-analyze
Startup finished in 6.250s (kernel) + 4.683s (userspace) = 10.933s
graphical.target reached after 4.664s in userspace

[m654321]

added noatime to the root partition

Coltman151, I was interested to see that you used "noatime" in your fstab file, to improve the reading/writing speeds of your SSD. I assume it's not in LL's fstab file by default because some users have an HDD instead of  an SSD. This prompted me to look at my own fstab file which looks like this, showing LL installed as root on sda2, and my DATA partition installed at sda7 [setup(1) in signature below]:

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=0db21fa8-d5a6-47e5-9e94-9795e9486c63 /               ext4    errors=remount-ro 0       1
/swapfile                                 none            swap    sw              0       0
# Automount partition, named G750_DATA at /dev/sda7, on booting as /media/DATA
UUID=0096b252-a4dd-43cd-bbe5-a4590da43c44 /media/DATA  ext4   defaults,noatime,auto 0     2

To add "noatime" to the root partition, as you have done, should I do it like this:  UUID=0db21fa8-d5a6-47e5-9e94-9795e9486c63 /    ext4    noatime,errors=remount-ro  0      1                     
Also should I add "defaults", as I've done for the DATA partition like this: UUID=0db21fa8-d5a6-47e5-9e94-9795e9486c63 /    ext4    defaults,noatime,errors=remount-ro  0      1 


Any feedback greatly appreciated

[coltman151]

Sorry for the slow reply! noatime is more for SSD longevity than speed, as it cuts out some extra writes that EXT4 do. However, here's my fstab file.

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=bd37f809-d366-4403-b977-c577adb3729c /               ext4    noatime,errors=remount-ro 0       1
/swapfile                                 none            swap    sw              0       0

It's my understanding that defaults shouldn't be there unless there are no other options.

[m654321]

[member=7759]coltman151[/member]

Many thanks for your reply, much appreciated, and for pointing out that noatime reduces wear-and-tear on the SSD by reducing the number of writes, and not speed ...

Have a great day  8)


Mike