tdpeuter/sisyphus
tdpeuter/sisyphus
1
Fork 0
Code Issues5 Pull requests Projects Releases Packages Wiki Activity

Home-manager boot slowdown #17

New issue
Open
opened 2025-01-09 10:27:56 +01:00 by tdpeuter · 1 comment
tdpeuter commented 2025-01-09 10:27:56 +01:00
Owner 
$ systemd-analyze blame
7.383s home-manager-tdpeuter.service
1.013s NetworkManager.service
 825ms systemd-rfkill.service
 792ms systemd-backlight@backlight:intel_backlight.service
 485ms firewall.service
 466ms modprobe@efi_pstore.service
 420ms dev-disk-by\x2dlabel-NIX\x2dROOT.device
 318ms vboxnet0.service
 300ms tailscaled.service
 287ms systemd-modules-load.service
 249ms user@1000.service
 222ms suid-sgid-wrappers.service
 183ms mount-pstore.service
 169ms systemd-backlight@leds:dell::kbd_backlight.service
 159ms systemd-udev-trigger.service
 156ms systemd-fsck@dev-disk-by\x2dlabel-NIX\x2dBOOT.service
 155ms NetworkManager-dispatcher.service
 152ms bluetooth.service
 150ms systemd-journal-flush.service
 147ms dbus.service
 147ms systemd-remount-fs.service
 124ms systemd-timesyncd.service
 123ms modprobe@fuse.service
  99ms systemd-journald.service
  85ms resolvconf.service
  82ms systemd-vconsole-setup.service
  74ms cpufreq.service
  65ms systemd-oomd.service
  65ms boot-efi.mount
  64ms polkit.service
  63ms network-setup.service
  63ms systemd-tmpfiles-setup.service
  61ms systemd-tmpfiles-setup-dev-early.service
  54ms systemd-logind.service
  54ms modprobe@drm.service
  52ms atd.service
  51ms network-addresses-vboxnet0.service
  51ms systemd-sysctl.service
  50ms systemd-udevd.service
``` $ systemd-analyze blame 7.383s home-manager-tdpeuter.service 1.013s NetworkManager.service 825ms systemd-rfkill.service 792ms systemd-backlight@backlight:intel_backlight.service 485ms firewall.service 466ms modprobe@efi_pstore.service 420ms dev-disk-by\x2dlabel-NIX\x2dROOT.device 318ms vboxnet0.service 300ms tailscaled.service 287ms systemd-modules-load.service 249ms user@1000.service 222ms suid-sgid-wrappers.service 183ms mount-pstore.service 169ms systemd-backlight@leds:dell::kbd_backlight.service 159ms systemd-udev-trigger.service 156ms systemd-fsck@dev-disk-by\x2dlabel-NIX\x2dBOOT.service 155ms NetworkManager-dispatcher.service 152ms bluetooth.service 150ms systemd-journal-flush.service 147ms dbus.service 147ms systemd-remount-fs.service 124ms systemd-timesyncd.service 123ms modprobe@fuse.service 99ms systemd-journald.service 85ms resolvconf.service 82ms systemd-vconsole-setup.service 74ms cpufreq.service 65ms systemd-oomd.service 65ms boot-efi.mount 64ms polkit.service 63ms network-setup.service 63ms systemd-tmpfiles-setup.service 61ms systemd-tmpfiles-setup-dev-early.service 54ms systemd-logind.service 54ms modprobe@drm.service 52ms atd.service 51ms network-addresses-vboxnet0.service 51ms systemd-sysctl.service 50ms systemd-udevd.service ```
tdpeuter added the
bug
 label 2025-01-09 10:28:33 +01:00
tdpeuter commented 2025-01-09 10:54:26 +01:00
Author
Owner

After disabling all home-manager.users.<user>.home.file.<path> in 6ef7e0aef8/nixos/users/tdpeuter/dotfiles.nix:

$ systemd-analyze blame
1.132s NetworkManager.service
 778ms systemd-backlight@backlight:intel_backlight.service
 738ms systemd-rfkill.service
 692ms home-manager-tdpeuter.service
 689ms systemd-backlight@leds:dell::kbd_backlight.service
 513ms firewall.service
 424ms vboxnet0.service
 413ms dev-disk-by\x2dlabel-NIX\x2dROOT.device
 362ms boot-efi.mount
 303ms tailscaled.service
 291ms systemd-modules-load.service
 252ms user@1000.service
 190ms suid-sgid-wrappers.service
 178ms mount-pstore.service
 152ms systemd-udev-trigger.service
 143ms systemd-journal-flush.service
 139ms systemd-remount-fs.service
 134ms NetworkManager-dispatcher.service
 131ms bluetooth.service
 125ms dbus.service
 112ms systemd-timesyncd.service
  99ms modprobe@fuse.service
  99ms systemd-fsck@dev-disk-by\x2dlabel-NIX\x2dBOOT.service
  95ms systemd-journald.service
  91ms systemd-hostnamed.service
  87ms run-wrappers.mount
  80ms systemd-vconsole-setup.service
  76ms resolvconf.service
  72ms cpufreq.service
  62ms systemd-tmpfiles-setup.service
  62ms network-setup.service
  61ms polkit.service
  54ms wpa_supplicant.service
  53ms network-addresses-vboxnet0.service
  52ms systemd-logind.service
  49ms systemd-udevd.service
  47ms systemd-oomd.service
  46ms systemd-tmpfiles-setup-dev.service
  45ms systemd-boot-random-seed.service
  41ms modprobe@drm.service
  40ms atd.service
  39ms systemd-sysctl.service
  35ms user-runtime-dir@1000.service
  35ms systemd-tmpfiles-setup-dev-early.service
  34ms systemd-random-seed.service
  33ms logrotate-checkconf.service
  32ms network-local-commands.service
  32ms systemd-user-sessions.service
  32ms audit.service
  31ms dev-disk-by\x2dlabel-SWAP.swap
  29ms systemd-update-utmp.service
  27ms modprobe@configfs.service
  27ms kmod-static-nodes.service
  24ms modprobe@efi_pstore.service
  19ms nscd.service
  17ms dev-mqueue.mount
  17ms dev-hugepages.mount
  17ms sys-kernel-debug.mount
  14ms sys-fs-fuse-connections.mount
  13ms sys-kernel-config.mount
  10ms docker.socket

Leftover time is probably still due to my mail config etc.

After disabling all `home-manager.users.<user>.home.file.<path>` in https://git.depeuter.dev/tdpeuter/sisyphus/src/commit/6ef7e0aef840affc1bd0c35165606ec4cd66c0d0/nixos/users/tdpeuter/dotfiles.nix: ``` $ systemd-analyze blame 1.132s NetworkManager.service 778ms systemd-backlight@backlight:intel_backlight.service 738ms systemd-rfkill.service 692ms home-manager-tdpeuter.service 689ms systemd-backlight@leds:dell::kbd_backlight.service 513ms firewall.service 424ms vboxnet0.service 413ms dev-disk-by\x2dlabel-NIX\x2dROOT.device 362ms boot-efi.mount 303ms tailscaled.service 291ms systemd-modules-load.service 252ms user@1000.service 190ms suid-sgid-wrappers.service 178ms mount-pstore.service 152ms systemd-udev-trigger.service 143ms systemd-journal-flush.service 139ms systemd-remount-fs.service 134ms NetworkManager-dispatcher.service 131ms bluetooth.service 125ms dbus.service 112ms systemd-timesyncd.service 99ms modprobe@fuse.service 99ms systemd-fsck@dev-disk-by\x2dlabel-NIX\x2dBOOT.service 95ms systemd-journald.service 91ms systemd-hostnamed.service 87ms run-wrappers.mount 80ms systemd-vconsole-setup.service 76ms resolvconf.service 72ms cpufreq.service 62ms systemd-tmpfiles-setup.service 62ms network-setup.service 61ms polkit.service 54ms wpa_supplicant.service 53ms network-addresses-vboxnet0.service 52ms systemd-logind.service 49ms systemd-udevd.service 47ms systemd-oomd.service 46ms systemd-tmpfiles-setup-dev.service 45ms systemd-boot-random-seed.service 41ms modprobe@drm.service 40ms atd.service 39ms systemd-sysctl.service 35ms user-runtime-dir@1000.service 35ms systemd-tmpfiles-setup-dev-early.service 34ms systemd-random-seed.service 33ms logrotate-checkconf.service 32ms network-local-commands.service 32ms systemd-user-sessions.service 32ms audit.service 31ms dev-disk-by\x2dlabel-SWAP.swap 29ms systemd-update-utmp.service 27ms modprobe@configfs.service 27ms kmod-static-nodes.service 24ms modprobe@efi_pstore.service 19ms nscd.service 17ms dev-mqueue.mount 17ms dev-hugepages.mount 17ms sys-kernel-debug.mount 14ms sys-fs-fuse-connections.mount 13ms sys-kernel-config.mount 10ms docker.socket ``` Leftover time is probably still due to my mail config etc.
tdpeuter changed title from Slow boot times to Home-manager boot slowdown 2025-01-09 10:57:01 +01:00
Sign in to join this conversation.
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tdpeuter/sisyphus#17
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?