Major increase in boot time after updating a fresh Solus Budgie installation

Jumpy

I've liked Solus for it's fast boot times. But it's no longer as fast as it used to be.

With a fresh installation from the latest ISO of Solus Budgie I get this boot time:

$ systemd-analyze
Startup finished in 3.630s (firmware) + 152ms (loader) + 1.399s (kernel) + 670ms (initrd) + 295ms (userspace) = 6.148s
graphical.target reached after 288ms in userspace

Then after "sudo eopkg up" and nothing else done I get this boot time:

$ systemd-analyze
Startup finished in 4.055s (firmware) + 166ms (loader) + 1.385s (kernel) + 1.057s (initrd) + 7.134s (userspace) = 13.800s
graphical.target reached after 7.124s in userspace

Why such a big increase with userspace? Can I do something to tweak it down? Or can the maintainers of Solus do something about this?

WetGeek

Jumpy

Jumpy, I don't have a real answer for you, but I thought I'd let you know that your userspace time isn't unusually long. This is from my laptop, which is quite robust (i7 processor, 16GB of RAM):

Seems pretty similar to me. By the way, this laptop uses Solus Plasma. I had just done a backup in the terminal, if that matters. If you learn of something that will speed up your reboot, please remember to post the answer here. Maybe it would be of interest to others.

Staudey

Well a first step would probably be to run systemd-analyze blame to see what exactly is taking so "long".

nolan

Staudey that's the way to follow.
A side note; I had a long boot time and that helped me to know where was the problem, it turned out that the swap partition wasn't correctly configured in fstab, the uuid for swap wasn't present, I've never touched it before, figure out how it happened, maybe an update?, using the correct uuid solved the long boot problem.

Jumpy

1) Before updates:

$ systemd-analyze blame
155ms initrd-switch-root.service 65ms udisks2.service 62ms upower.service 59ms initrd-parse-etc.service 57ms lightdm.service 51ms user@1000.service

2e90\x2d8a8e\x2d4680\x2d85c8\x2ddb81d1717d0a.swap

@configfs.service">modprobe@configfs.service
@drm.service">modprobe@drm.service
@fuse.service">modprobe@fuse.service

time-dir@1000.service">user-runtime-dir@1000.service
ght:acpi_video0.service

ght:acpi_video1.service

2) After updates

8.042s NetworkManager-wait-online.service
256ms apparmor.service
155ms initrd-switch-root.service
102ms systemd-udev-trigger.service
87ms systemd-journal-flush.service
79ms aa-lsm-hook.service
58ms udisks2.service
54ms initrd-parse-etc.service
49ms user@1000.service
46ms lightdm.service
33ms upower.service
30ms systemd-udevd.service
27ms ModemManager.service
25ms auditd.service
24ms bluetooth.service
22ms systemd-rfkill.service
21ms polkit.service
21ms systemd-logind.service
19ms NetworkManager.service
18ms systemd-tmpfiles-setup.service
18ms systemd-fsck-root.service
15ms systemd-random-seed.service
14ms systemd-tmpfiles-setup-dev.service
14ms bolt.service
12ms colord.service
11ms initrd-cleanup.service
11ms power-profiles-daemon.service
10ms org.cups.cupsd.service
8ms systemd-sysctl.service
8ms accounts-daemon.service
8ms dev-disk-by\x2duuid-18e22e90\x2d8a8e\x2d4680\x2d85c8\x2ddb81d1717d0a.swap
8ms dev-hugepages.mount
8ms dev-mqueue.mount
7ms sys-kernel-debug.mount
7ms sys-kernel-tracing.mount
6ms systemd-boot-system-token.service
6ms kmod-static-nodes.service
6ms modprobe@configfs.service
5ms clr-boot-manager-booted.service
5ms modprobe@drm.service
5ms modprobe@fuse.service
5ms rtkit-daemon.service
5ms systemd-journald.service
4ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount
4ms systemd-remount-fs.service
4ms systemd-update-utmp-runlevel.service
4ms wpa_supplicant.service
3ms systemd-update-utmp.service
3ms tmp.mount
3ms user-runtime-dir@1000.service
3ms avahi-daemon.service
3ms systemd-backlight@backlight:acpi_video0.service
2ms systemd-user-sessions.service
2ms systemd-backlight@backlight:acpi_video1.service
2ms alsa-restore.service
1ms initrd-udevadm-cleanup-db.service
1ms systemd-vconsole-setup.service
355us snapd.socket

What is the deal?

WetGeek

Jumpy What is the deal?

Dunno. But if we have an update tomorrow, I'm going to do a similar before and after. I can't imagine why that "after" list is so long. I want to see if it happens here.

Jumpy

Any ideas how to get rid off "6.721s NetworkManager-wait-online.service"?

Jumpy

UPDATE. The height of the terminal window does something weird. If I stretch it big the after update listing for "$ systemd-analyze blame" is:

[Staudey: I edited your original message to only include the actual list you posted in this comment, and not the one with endlessly repeating items so this thread is a bit more readable]

Jumpy

I found this tip: "sudo systemctl disable NetworkManager-wait-online.service"

After running that I'am back to the original boot times:

$ systemd-analyze
Startup finished in 3.869s (firmware) + 157ms (loader) + 1.369s (kernel) + 1.057s (initrd) + 465ms (userspace) = 6.919s
graphical.target reached after 456ms in userspace

$ systemd-analyze blame
248ms apparmor.service
161ms initrd-switch-root.service
119ms systemd-hostnamed.service
71ms udisks2.service
68ms aa-lsm-hook.service
66ms systemd-udev-trigger.service
59ms systemd-journal-flush.service
57ms initrd-parse-etc.service
52ms lightdm.service
51ms user@1000.service
36ms systemd-localed.service
36ms systemd-timedated.service
35ms ModemManager.service
34ms bluetooth.service
32ms systemd-udevd.service
30ms upower.service
29ms systemd-tmpfiles-setup.service
28ms auditd.service
27ms systemd-logind.service
20ms NetworkManager.service
19ms systemd-tmpfiles-setup-dev.service
18ms systemd-fsck-root.service
17ms polkit.service
14ms systemd-random-seed.service
14ms bolt.service
12ms initrd-cleanup.service
11ms accounts-daemon.service
11ms org.cups.cupsd.service
10ms power-profiles-daemon.service
8ms dev-hugepages.mount
8ms colord.service
8ms dev-disk-by\x2duuid-18e22e90\x2d8a8e\x2d4680\x2d85c8\x2ddb81d1717d0a.swap
8ms dev-mqueue.mount
8ms sys-kernel-debug.mount
7ms systemd-rfkill.service
7ms sys-kernel-tracing.mount
6ms systemd-boot-system-token.service
6ms kmod-static-nodes.service
6ms modprobe@configfs.service
6ms modprobe@drm.service
5ms modprobe@fuse.service
5ms clr-boot-manager-booted.service
5ms systemd-journald.service
4ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount
4ms systemd-remount-fs.service
4ms avahi-daemon.service
4ms systemd-sysctl.service
4ms rtkit-daemon.service
3ms systemd-update-utmp.service
3ms wpa_supplicant.service
3ms tmp.mount
3ms user-runtime-dir@1000.service
2ms alsa-restore.service
2ms systemd-backlight@backlight:acpi_video0.service
2ms systemd-update-utmp-runlevel.service
2ms systemd-backlight@backlight:acpi_video1.service
2ms systemd-user-sessions.service
1ms initrd-udevadm-cleanup-db.service
1ms systemd-vconsole-setup.service
311us snapd.socket

nolan

A quick search on duckduckgo:

NetworkManager-wait-online.service delays network-online.target until network is ready.
The systemd target network-online.target acts as a synchronization point for services to start after network is configured.
taked from: https://networkmanager.pages.freedesktop.org/NetworkManager/NetworkManager/NetworkManager-wait-online.service.html

On simple terms (correct me if I'm wrong) NetworkManager-wait-online.service waits for the computer to be conectet to the network then continue booting.

And some forum I found suggest to mask that service.
This is some of them (4 years ago.)
https://askubuntu.com/questions/1018576/what-does-networkmanager-wait-online-service-do
https://forums.linuxmint.com/viewtopic.php?t=282437

WetGeek

nolan NetworkManager-wait-online.service delays network-online.target until network is ready.

Interesting! As in "wait until the network's ready before you try to mount those NAS shares."