Machines vastly differ in hardware components:
erlangen:~ # inxi -zFm
System: Kernel: 5.11.15-1-default x86_64 bits: 64 Console: tty pts/1 Distro: openSUSE Tumbleweed 20210418
Machine: Type: Desktop Mobo: ASRock model: Z170 Pro4S serial: <filter> UEFI: American Megatrends v: P3.50 date: 06/23/2016
Memory: RAM:total: 31.3 GiB used: 4.33 GiB (13.8%)
Array-1:capacity: 64 GiB slots: 4 EC: None
Device-1: ChannelA-DIMM0 size: No Module Installed
Device-2: ChannelA-DIMM1 size: 16 GiB speed: 2133 MT/s
Device-3: ChannelB-DIMM0 size: No Module Installed
Device-4: ChannelB-DIMM1 size: 16 GiB speed: 2133 MT/s
CPU: Info: Quad Core model: Intel Core i7-6700K bits: 64 type: MT MCP cache:L2: 8 MiB
Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz):1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
Graphics: Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] driver: amdgpu v: kernel
Display:server: X.Org 1.20.10 driver:loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa
resolution: 3840x2160~60Hz
OpenGL:renderer: Radeon RX550/550 Series (POLARIS12 DRM 3.40.0 5.11.15-1-default LLVM 11.0.1) v: 4.6 Mesa 21.0.2
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel
Device-2: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] driver: snd_hda_intel
Sound Server-1: ALSA v: k5.11.15-1-default running: yes
Sound Server-2: PulseAudio v: 14.2-rebootstrapped running: yes
Network: Device-1: Intel Ethernet I219-V driver: e1000e
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage:total: 6.38 TiB used: 3.13 TiB (49.1%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 950 PRO 512GB size: 476.94 GiB
ID-2: /dev/sda vendor: Western Digital model: WD40EZRX-22SPEB0 size: 3.64 TiB
ID-3: /dev/sdb vendor: Crucial model: CT2000BX500SSD1 size: 1.82 TiB
ID-4: /dev/sdc vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
Partition: ID-1: / size: 51.69 GiB used: 21.96 GiB (42.5%) fs: btrfs dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 99.8 MiB used: 15.3 MiB (15.3%) fs: vfat dev: /dev/nvme0n1p1
ID-3: /home size: 406.34 GiB used: 292.62 GiB (72.0%) fs: ext4 dev: /dev/nvme0n1p4
ID-4: /opt size: 51.69 GiB used: 21.96 GiB (42.5%) fs: btrfs dev: /dev/nvme0n1p3
ID-5: /var size: 51.69 GiB used: 21.96 GiB (42.5%) fs: btrfs dev: /dev/nvme0n1p3
Swap: Alert: No Swap data was found.
Sensors: System Temperatures:cpu: 32.0 C mobo: 33.0 C gpu: amdgpu temp: 53.0 C
Fan Speeds (RPM):fan-1: 0 fan-2: 1187 fan-3: 0 fan-4: 0 fan-5: 0 fan-6: 0 gpu: amdgpu fan: 965
Info: Processes: 280 Uptime: 9h 51m Shell: Bash inxi: 3.3.03
erlangen:~ #
On host erlangen many services are running in parallel. Nevertheless no delay occurs on boot up in kde:
erlangen:~ # systemd-analyze blame |head -22
2min 11.285s backup-home.service
36.554s purge-kernels.service
28.072s mlocate.service
15.711s backup-rpmdb.service
9.949s HDD.mount
8.733s mandb.service
1.540s logrotate.service
963ms dracut-initqueue.service
909ms dracut-pre-udev.service
708ms display-manager.service
587ms initrd-switch-root.service
552ms postfix.service
448ms udisks2.service
391ms lm_sensors.service
318ms systemd-journal-flush.service
292ms apparmor.service
287ms plymouth-quit-wait.service
209ms systemd-resolved.service
202ms initrd-parse-etc.service
177ms mcelog.service
139ms systemd-logind.service
135ms user@1000.service
erlangen:~ #
Display manager is up early. Login and startup of the graphical session is fast:
erlangen:~ # systemd-analyze critical-chain display-manager.service
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.
display-manager.service +708ms
└─apache2.service @1.055s +68ms
└─time-sync.target @1.050s
└─chronyd.service @1.019s +30ms
└─nss-lookup.target @1.018s
└─systemd-resolved.service @809ms +209ms
└─systemd-tmpfiles-setup.service @792ms +15ms
└─systemd-journal-flush.service @473ms +318ms
└─var.mount @464ms +7ms
└─local-fs-pre.target @457ms
└─systemd-tmpfiles-setup-dev.service @442ms +14ms
└─kmod-static-nodes.service @400ms +32ms
└─systemd-journald.socket
└─-.mount
└─system.slice
└─-.slice
erlangen:~ #
Fstrim runs in the background and I never notice any delays of the graphical interface:
erlangen:~ # journalctl -b -1 -u fstrim.service
-- Logs begin at Wed 2021-03-24 04:52:44 CET, end at Wed 2021-04-21 06:33:08 CEST. --
Apr 19 05:39:00 erlangen systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Apr 19 05:45:11 erlangen fstrim[4578]: /home-SSD: 575,4 GiB (617788227584 Bytes) auf /dev/sdb1 getrimmt
Apr 19 05:45:11 erlangen fstrim[4578]: /boot/efi: 84,5 MiB (88600576 Bytes) auf /dev/nvme0n1p1 getrimmt
Apr 19 05:45:11 erlangen fstrim[4578]: /home: 113,7 GiB (122039463936 Bytes) auf /dev/nvme0n1p4 getrimmt
Apr 19 05:45:11 erlangen fstrim[4578]: /: 11,1 GiB (11904901120 Bytes) auf /dev/nvme0n1p3 getrimmt
Apr 19 05:45:11 erlangen systemd[1]: fstrim.service: Succeeded.
Apr 19 05:45:11 erlangen systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.
Apr 19 05:45:11 erlangen systemd[1]: fstrim.service: Consumed 8.403s CPU time.
erlangen:~ #
Sizes of trimmed partition are:
erlangen:~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p3 52G 22G 28G 45% /
/dev/nvme0n1p1 100M 16M 85M 16% /boot/efi
/dev/nvme0n1p4 407G 293G 113G 73% /home
/dev/sdb1 1.8T 1.3T 483G 73% /home-SSD
erlangen:~ #
Btrfs maintenance is also fast and unobtrusive:
erlangen:~ # journalctl -b -u btrfs* --grep Consumed
-- Logs begin at Wed 2021-03-24 04:52:44 CET, end at Wed 2021-04-21 06:33:08 CEST. --
Apr 21 05:12:50 erlangen systemd[1]: btrfs-defrag.service: Consumed 7.940s CPU time.
Apr 21 05:13:52 erlangen systemd[1]: btrfs-trim.service: Consumed 3.144s CPU time.
Apr 21 05:14:05 erlangen systemd[1]: btrfs-scrub.service: Consumed 4.041s CPU time.
erlangen:~ #
I presume your machine runs out of resources. Of course you always can run your services at your own schedule. Modify the timers accordingly.