Speed up boot time and shutdown?

inxi -Fza
System:    Kernel: 5.13.8-2-cacule x86_64 bits: 64 compiler: gcc v: 11.1.0 
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-cacule 
root=UUID=d705e742-9d27-4001-909a-c8b33abd69ac rw [email protected] quiet splash 
rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 
resume=UUID=d2c6afb2-b903-4bf2-9889-2eb2819f64fa loglevel=3 
Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM 
Distro: Garuda Linux base: Arch Linux 
Machine:   Type: Laptop System: ASUSTeK product: X510UA v: 1.0 serial: <filter> 
Mobo: ASUSTeK model: X510UA v: 1.0 serial: <filter> UEFI: American Megatrends v: X510UA.312 
date: 04/29/2020 
Battery:   ID-1: BAT0 charge: 10.0 Wh (31.9%) condition: 31.3/42.1 Wh (74.4%) volts: 11.5 min: 11.5 
model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Discharging cycles: 383 
CPU:       Info: Dual Core model: Intel Core i7-7500U bits: 64 type: MT MCP arch: Amber/Kaby Lake 
note: check family: 6 model-id: 8E (142) stepping: 9 microcode: EA cache: L2: 4 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23199 
Speed: 759 MHz min/max: 400/2700 MHz Core speeds (MHz): 1: 759 2: 784 3: 642 4: 800 
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
Type: meltdown mitigation: PTI 
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
Type: spectre_v2 
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
Type: srbds mitigation: Microcode 
Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0 
chip-ID: 8086:5916 class-ID: 0300 
Device-2: IMC Networks VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-6:2 
chip-ID: 13d3:5a07 class-ID: 0e02 serial: <filter> 
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: intel 
unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1 
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") 
Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 143 size: 340x190mm (13.4x7.5") diag: 389mm (15.3") 
OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.1.6 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
alternate: snd_soc_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403 
Sound Server-1: ALSA v: k5.13.8-2-cacule running: yes 
Sound Server-2: JACK v: 1.9.19 running: no 
Sound Server-3: PulseAudio v: 15.0 running: no 
Sound Server-4: PipeWire v: 0.3.33 running: yes 
Network:   Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: f040 bus-ID: 02:00.0 
chip-ID: 8086:24fd class-ID: 0280 
IF: wlp2s0 state: up mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-8:3 
chip-ID: 8087:0a2b class-ID: e001 
Report: bt-adapter ID: hci0 rfk-id: 1 state: down bt-service: enabled,running rfk-block: 
hardware: no software: yes address: <filter> 
Drives:    Local Storage: total: 704.24 GiB used: 56.48 GiB (8.0%) 
SMART Message: Unable to run smartctl. Root privileges required. 
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1B6Q
scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Micron model: 1100 MTFDDAV256TBN size: 238.47 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: A020
scheme: GPT
Partition: ID-1: / raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 56.48 GiB (12.6%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 563 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 56.48 GiB (12.6%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 56.48 GiB (12.6%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 448.43 GiB size: 448.43 GiB (100.00%) used: 56.48 GiB (12.6%)
fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 17.07 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3
maj-min: 8:3
ID-2: swap-2 type: zram size: 15.53 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2500
Info:      Processes: 233 Uptime: 15m wakeups: 1 Memory: 15.53 GiB used: 3.24 GiB (20.9%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1403 lib: 345
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06

╭─[email protected] in ~/.local/share/applications took 2s

Hey, so first of all I want to say that Garuda has become my favourite Linux Distro. It's the only one based on Arch where I haven't had problems, even when Manjaro has in the past. And I love the theming and GUI tools and customisation and basically everything about it. Just wanted to make that clear so that it's understood I do love the distro and appreciate the work from the developers and testers.

I do have one sllght problem though. Garuda is exceptionally higher in terms of boot time and shutdown time than Manjaro, KDE, Ubuntu, Debian, PopOS and basically any distro I have used in the past. I don't know why this is as there is a focus on performance so I figured it would be faster not slower. Is it because the distro is sloghtly bloated with a lot of software? Or something to do with Btrfs filesystem maybe? I ask, because similar posts have been made but with no real answer as to why this is the case and how to potentially get boot and shitdown times on a similar level of other distros. Some information would be apprecaiated as to why it is significantly slower and potential ways to decrease these times would be great.

Here a couple of threads reviews to show it is not just a couple of people but a possible majority if not all?

Blockquote "Garuda Linux also advertises itself as a performance-focused distro, but I didn’t feel any of that. Quite the contrary, to some extent. For example, boot time is very long. I run KDE Neon on the same machine, and it boots noticeably faster. Shutdown time is also longer." https://averagelinuxuser.com/garuda-linux-distro/

1 Like

I am fine :slight_smile:

systemd-analyze
Startup finished in 12.008s (firmware) + 6.711s (loader) + 2.058s (kernel) + 2.044s (userspace) = 22.822s 
graphical.target reached after 2.007s in userspace

Post your systemd-analyze blame

 ╭─[email protected] in ~ took 3ms
 ╰─λ systemd-analyze blame
561ms mnt-sda3.mount
434ms udisks2.service
154ms dev-nvme0n1p2.device
144ms mnt-sda1.mount
123ms mnt-sda2.mount
121ms pamac-cleancache.service
104ms memavaild.service
 89ms cups.service
 83ms [email protected]ram0.service
 80ms systemd-journal-flush.service
 68ms systemd-remount-fs.service
 67ms [email protected]
 61ms systemd-modules-load.service
 51ms systemd-udev-trigger.service
 34ms accounts-daemon.service
 30ms systemd-timesyncd.service
 29ms systemd-journald.service
 27ms systemd-logind.service
 27ms systemd-vconsole-setup.service
 27ms upower.service
 26ms mnt-nvme1.mount
 25ms polkit.service
 25ms NetworkManager.service
 24ms systemd-udevd.service
 19ms [email protected]\x2duuid-B3B3\x2dD44D.service
 19ms lightdm-plymouth.service
 19ms boot-efi.mount
 19ms dev-zram0.swap
 19ms mnt-sdb2.mount
 18ms sys-fs-fuse-connections.mount
 18ms plymouth-quit-wait.service
 17ms lm_sensors.service
 14ms systemd-random-seed.service
 14ms plymouth-start.service
 11ms avahi-daemon.service
 11ms systemd-tmpfiles-setup.service
 10ms plymouth-read-write.service
  9ms systemd-tmpfiles-clean.service
  6ms colord.service
  6ms [email protected]
  5ms systemd-tmpfiles-setup-dev.service
  5ms [email protected]
  4ms linux-modules-cleanup.service
  4ms systemd-sysctl.service
  4ms [email protected]
  3ms dev-hugepages.mount
  3ms dev-mqueue.mount
  3ms root.mount
  3ms sys-kernel-debug.mount
  3ms [email protected]\x2duuid-35075ddb\x2dbcf7\x2d47aa\x2da43a\x2de759a082>
  3ms srv.mount
  3ms home.mount
  3ms kmod-static-nodes.service
  2ms var-cache.mount
  2ms [email protected]
  2ms systemd-update-utmp.service
  2ms [email protected]
  2ms var-log.mount
  2ms systemd-user-sessions.service
  2ms rtkit-daemon.service
  2ms tmp.mount
  2ms var-tmp.mount
  1ms systemd-rfkill.service
863us sys-kernel-config.mount
3 Likes
Startup finished in 3.764s (firmware) + 8.260s (loader) + 1.608s (kernel) + 33.240s (userspace) = 46.873s
graphical.target reached after 33.240s in userspace
systemd-analyze blame
30.539s systemd-networkd-wait-online.service
4.039s NetworkManager-wait-online.service
1.852s lvm2-monitor.service
1.718s dev-sda2.device
1.514s linux-modules-cleanup.service
969ms systemd-remount-fs.service
621ms grub-btrfs.service
359ms systemd-logind.service
256ms systemd-modules-load.service
245ms plymouth-start.service
234ms systemd-tmpfiles-clean.service
207ms tlp.service
207ms systemd-udev-trigger.service
194ms polkit.service
156ms ModemManager.service
145ms upower.service
143ms NetworkManager.service
137ms avahi-daemon.service
120ms [email protected]
114ms memavaild.service
113ms systemd-binfmt.service
112ms bluetooth.service
108ms systemd-user-sessions.service
107ms plymouth-deactivate.service
106ms plymouth-quit-wait.service
104ms plymouth-quit.service
90ms [email protected]
85ms plymouth-read-write.service
81ms [email protected]\x2duuid-C67B\x2d1D79.service
72ms systemd-journal-flush.service
69ms systemd-timesyncd.service
67ms sys-fs-fuse-connections.mount
66ms systemd-tmpfiles-setup.service
66ms sys-kernel-config.mount
66ms smb.service
65ms proc-sys-fs-binfmt_misc.mount
65ms udisks2.service
59ms systemd-networkd.service
59ms systemd-udevd.service
58ms systemd-vconsole-setup.service
57ms systemd-journald.service
48ms systemd-guest-user.service
46ms systemd-guest-config.service
45ms nmb.service
32ms [email protected]
27ms [email protected]:intel_backlight.service
23ms systemd-rfkill.service
22ms srv.mount
21ms pamac-daemon.service
20ms systemd-sysctl.service
19ms var-cache.mount
18ms dev-binderfs.mount
18ms dev-hugepages.mount
18ms var-log.mount
17ms dev-mqueue.mount
17ms boot-efi.mount
17ms sys-kernel-debug.mount
16ms home.mount
15ms kmod-static-nodes.service
15ms root.mount
14ms [email protected]
13ms tmp.mount
13ms colord.service
13ms var-tmp.mount
13ms cups.service
12ms [email protected]
11ms [email protected]
11ms [email protected]
11ms [email protected]:asus::kbd_backlight.service
9ms systemd-random-seed.service
9ms systemd-update-utmp.service
9ms systemd-tmpfiles-setup-dev.service
8ms dev-disk-by\x2duuid-d2c6afb2\x2db903\x2d4bf2\x2d9889\x2d2eb2819f64fa.swap
7ms dev-zram0.swap
7ms home-guest.mount
5ms rtkit-daemon.service
4ms wpa_supplicant.service
3 Likes

Not sure what you mean in terms of the first part of that comment. And I don't kow if my Wifi is doing what you are saying or if I can check that or fix it or not.

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 @33.240s
└─multi-user.target @33.240s
└─smb.service @33.173s +66ms
└─nmb.service @33.126s +45ms
└─network-online.target @33.123s
└─systemd-networkd-wait-online.service @2.583s +30.539s
└─systemd-networkd.service @2.522s +59ms
└─systemd-udevd.service @2.457s +59ms
└─systemd-tmpfiles-setup-dev.service @2.443s +9ms
└─kmod-static-nodes.service @1.463s +15ms
└─systemd-journald.socket @1.458s
└─system.slice @1.454s
└─-.slice @1.454s

╭─[email protected] in ~ took 314ms

Mask or disable everything you do not use, check what you have in other distros critical-chain.

2 Likes

Honestly I don't have a clue. I'll take a look but I'm confused as hell haha

Archwiki is your friend,
https://wiki.archlinux.org/title/Systemd

2 Likes

You reach graphical target (DM mostly) in 31 seconds.
networkd-wait-online takes 30.5 of them.

If you disable it, usually nothing goes wrong.
Disable the service and reboot to check.
If something breaks (on your system), re-enable it (in TTY, if you get in trouble).

Arch is for the brave! :rofl: No risk, no knowledge, no gain. :man_shrugging:

Ask elsewhere, if you don't trust. :grinning_face_with_smiling_eyes:

8 Likes

One thing I always do is maskimg lvm2-* services as I don't use them (comparable to systemd-networkd-wait-online).

3 Likes

Definetly True :100:

But which contributes more , user intervention needed or lack of systemd maintenance software like in Task Manager ( Service ) :thinking: . Yes there is terminal way , Service , task isn't documented , Yet atleast need some clue ryt like User , essential system process like load mount ,non essential system process plymoth , user essential like plasma & user non essential like ufw uf not used

Are you using dual boot? If yes you are going to encounter this issue.

Make sure fast boot and secure boot are turned off.

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