You are not logged in.
Pages: 1
Hello, I've been using Arch for about a year now, but only now I have gotten around to optimizing my boot time.
So far, disabling a Wait Online service shaved 4 seconds off the boot time. What else can I improve?
System info is:
KDE Plasma,
Ryzen 5 2600, Radeon RX 570
16GB of 3200mhz RAM
Boot drive is 120G SSD, pretty filled up but not completely.
Network is connected via RJ-45 cable. No other network adapters plugged in.
Output of systemd-analyze:
Startup finished in 10.088s (firmware) + 1.269s (loader) + 2.887s (kernel) + 2.316s (userspace) = 16.561s
graphical.target reached after 2.315s in userspaceOutput of systemd-analyze blame:
1.100s udisks2.service
897ms systemd-random-seed.service
548ms lvm2-monitor.service
488ms dhcpcd.service
360ms upower.service
328ms user@1000.service
326ms dev-sdc2.device
267ms home-gustavs-raspberrypi\x2dserver.mount
207ms systemd-journal-flush.service
176ms systemd-udevd.service
168ms systemd-fsck@dev-disk-by\x2dlabel-LinuxHome.service
150ms efi.mount
127ms NetworkManager.service
121ms systemd-logind.service
120ms systemd-machined.service
97ms polkit.service
72ms systemd-timesyncd.service
65ms systemd-journald.service
60ms systemd-udev-trigger.service
50ms modprobe@drm.service
45ms systemd-tmpfiles-setup.service
44ms home.mount
43ms systemd-fsck@dev-sdc1.service
41ms systemd-modules-load.service
32ms modprobe@fuse.service
31ms systemd-tmpfiles-setup-dev.service
28ms systemd-binfmt.service
23ms dev-hugepages.mount
23ms dev-mqueue.mount
22ms sys-kernel-debug.mount
22ms sys-kernel-tracing.mount
21ms kmod-static-nodes.service
21ms tmp.mount
20ms modprobe@configfs.service
12ms user-runtime-dir@1000.service
11ms proc-sys-fs-binfmt_misc.mount
11ms sys-kernel-config.mount
6ms systemd-update-utmp.service
6ms systemd-remount-fs.service
5ms systemd-sysctl.service
3ms rtkit-daemon.service
2ms systemd-user-sessions.service
2ms sys-fs-fuse-connections.mountIf you need any additional info, I'll try my best to provide it.
Offline
Look at the critical chain to see what's currently stalling your boot. Focus on that.
Offline
This is the output:
graphical.target @2.315s
└─sddm.service @2.315s
└─systemd-user-sessions.service @2.310s +2ms
└─network.target @1.893s
└─dhcpcd.service @1.403s +488ms
└─basic.target @1.400s
└─sockets.target @1.400s
└─virtlogd.socket @1.400s
└─sysinit.target @1.398s
└─systemd-timesyncd.service @1.326s +72ms
└─systemd-tmpfiles-setup.service @1.276s +45ms
└─local-fs.target @1.275s
└─home.mount @1.229s +44ms
└─systemd-fsck@dev-disk-by\x2dlabel-LinuxHome.service @1.058s +168ms
└─local-fs-pre.target @1.056s
└─lvm2-monitor.service @507ms +548ms
└─lvm2-lvmetad.service @750ms
└─systemd-udevd.service @573ms +176ms
└─systemd-tmpfiles-setup-dev.service @540ms +31ms
└─kmod-static-nodes.service @506ms +21ms
└─systemd-journald.socket @501ms
└─-.mount @483ms
└─-.slice @483msOffline
If you don't need lvm, you could mask that.
https://bbs.archlinux.org/viewtopic.php?id=263539
But the system boots fast, the slow parts will be SDDM and whatever your session is (plasma, I assume)
Offline
You could try not having any compression on the initrd images. Not using LVM should also speed up boot times. Switching to multi-user.target and using startx should help as well.
Offline
Pages: 1