Help needed in optimising boot process

Hello manjaro community,

I am using manjaro for a long time now…and I am enjoying it.
For quite some time I ignored the long booting up of my machine, I usually do not turn off my laptop, I put it into sleep mode. but I think it’s time now I explore the boot processes and optimise them for better use. This will be a learning curve for me.
I usually try to do it myself, but the system is running well, so I don’t want to mess up anything without expert guidance. so here we go…
I am putting some output here from my console…if any more information requires I will provide it in a jiffy…

[sonal@sonal-80e5 ~]$  systemd-analyze       
Startup finished in 4.036s (firmware) + 2.001s (loader) + 3.941s (kernel) + 1min 20.179s (userspace) = 1min 30.158s 
graphical.target reached after 1min 19.235s in userspace

[sonal@sonal-80e5 ~]$  systemd-analyze blame             
1min 1.426s systemd-swap.service                                 
    12.301s udisks2.service                                      
     9.095s lvm2-monitor.service                                 
     6.555s dev-sda3.device                                      
     5.989s polkit.service                                       
     3.685s bluetooth.service                                    
     3.684s avahi-daemon.service                                 
     3.680s NetworkManager.service                               
     3.554s systemd-logind.service                               
     2.825s systemd-journal-flush.service                        
     2.763s systemd-udevd.service                                
     2.708s ModemManager.service                                 
     2.449s cups.service                                         
     2.399s ufw.service                                          
     2.398s systemd-fsck@dev-disk-by\x2duuid-28CB\x2d1A14.service
     2.044s upower.service                                       
     2.044s apparmor.service                                     
     1.310s var-lib-snapd-snap-core18-2066.mount                 
     1.094s var-lib-snapd-snap-core18-1997.mount                 
     1.068s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount
     1.044s systemd-backlight@backlight:intel_backlight.service  
     1.029s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1515.mount
     1.015s wpa_supplicant.service                               
lines 1-23

[sonal@sonal-80e5 ~]$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 19.235s
└─multi-user.target @1min 19.235s
  └─systemd-swap.service @17.809s +1min 1.426s
    └─basic.target @17.673s
      └─sockets.target @17.673s
        └─dbus.socket @17.673s
          └─sysinit.target @17.640s
            └─systemd-update-utmp.service @17.601s +37ms
              └─systemd-tmpfiles-setup.service @17.078s +505ms
                └─local-fs.target @17.077s
                  └─boot-efi.mount @16.777s +300ms
                    └─systemd-fsck@dev-disk-by\x2duuid-28CB\x2d1A14.service @14.337s +2.398s
                      └─local-fs-pre.target @14.199s
                        └─lvm2-monitor.service @5.104s +9.095s
                          └─systemd-journald.socket @5.022s
                            └─system.slice @4.870s
                              └─-.slice @4.870s
[sonal@sonal-80e5 ~]$ 

Also, I am using systemd-swap with zswap.

thank you in advance :wink:

If you don’t use volumes than you can mask that service

this can also be masked.

systemctl mask <service_name>

Is your system using a SSD or HDD ? Also, i find that zram-generator to give a bit better performance … but you have to drop/uninstall systemd-swap
https://wiki.archlinux.org/title/Swap#zram-generator

1 Like

Reduce the number of used devices to 1 (zram_count=1) , that will sahave off a huge amount of time.
Multiple devices bring no performance benefit, the default is “sub-optimal”:

2 Likes

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.