LINUX.ORG.RU
Форум — Desktop  

время загрузки после обновления деб10>11

 ,


0

1

После обновления стало дольше грузится. Что можно отключить?

grovekeeper@debian:~$ systemd-analyze blame
20.791s udisks2.service
16.500s accounts-daemon.service
10.449s dev-sdb3.device
10.444s avahi-daemon.service
10.369s NetworkManager.service
10.331s systemd-journal-flush.service
10.138s wpa_supplicant.service
10.138s systemd-logind.service
 9.184s exim4-base.service
 8.478s smartmontools.service
 7.574s lightdm.service
 7.565s plymouth-quit-wait.service
 5.665s tdm.service
 4.569s rsyslog.service
 4.281s logrotate.service
 4.173s systemd-udevd.service
 3.958s exim4.service
 3.290s e2scrub_reap.service
 3.233s apparmor.service
 2.973s networking.service
 2.692s user@1000.service
 1.518s systemd-modules-load.service
 1.360s lm-sensors.service
 1.175s keyboard-setup.service
  896ms systemd-udev-trigger.service
  793ms systemd-tmpfiles-setup-dev.service
  778ms systemd-tmpfiles-setup.service
  744ms systemd-random-seed.service
  706ms lvm2-monitor.service
  702ms modprobe@fuse.service
  690ms systemd-sysusers.service
  615ms polkit.service
  595ms upower.service
  527ms console-setup.service
  512ms plymouth-start.service
  443ms systemd-sysctl.service
  400ms plymouth-read-write.service
  369ms systemd-remount-fs.service
  299ms systemd-timesyncd.service
  291ms systemd-journald.service
  289ms rtkit-daemon.service
  287ms ifupdown-pre.service


grovekeeper@debian:~$ 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 @40.565s
└─udisks2.service @19.773s +20.791s
  └─basic.target @19.388s
    └─sockets.target @19.388s
      └─uuidd.socket @19.388s
        └─sysinit.target @19.203s
          └─systemd-timesyncd.service @18.903s +299ms
            └─systemd-tmpfiles-setup.service @18.063s +778ms
              └─systemd-journal-flush.service @7.730s +10.331s
                └─systemd-remount-fs.service @7.213s +369ms
                  └─systemd-journald.socket @6.962s
                    └─-.mount @6.208s
                      └─-.slice @6.208s
grovekeeper@debian:~$ 


grovekeeper@debian:~$ systemd-analyze
Startup finished in 7.346s (kernel) + 40.595s (userspace) = 47.941s 
graphical.target reached after 40.565s in userspace

← flatpak разные версии одной и той же программы
Автомонтирование разделов в i3 с помощью devmon+udevil →

Ответ на: комментарий от Dumppper001

что поделаешь, не мы такие, а линукс)

MiST
() автор топика

после обновления

семи летний sid переживший следущие этапы трансформации sid > jessie > sid > stretch > sid > buster > sid > bullseye

$_systemd-analyze blame
3.583s dev-sdb1.device
2.870s systemd-journal-flush.service
1.984s NetworkManager.service
1.763s systemd-random-seed.service
1.672s nvidia-persistenced.service
1.621s systemd-modules-load.service
1.587s polkit.service
1.509s avahi-daemon.service
1.508s smartmontools.service
1.489s dhcpcd.service
1.436s systemd-logind.service
1.431s wpa_supplicant.service
1.065s tlp.service
 993ms systemd-udevd.service
 934ms apt-daily-upgrade.service
 768ms networking.service
 758ms rsyslog.service
 652ms lm-sensors.service
 584ms e2scrub_reap.service
 512ms keyboard-setup.service
 508ms user@1000.service
 443ms ModemManager.service
 442ms apparmor.service
 408ms systemd-tmpfiles-setup-dev.service
 256ms systemd-udev-trigger.service
 229ms systemd-journald.service
 216ms systemd-tmpfiles-setup.service
 181ms dev-disk-by\x2duuid-ee9858c7\x2d17a0\x2d4141\x2da2a9\x2d12c06e3b86af.swap
 179ms systemd-sysusers.service
 174ms modprobe@drm.service
 165ms modprobe@fuse.service
 149ms systemd-sysctl.service
 144ms media-sdX3.mount
 131ms ifupdown-pre.service
 124ms systemd-remount-fs.service
 119ms binfmt-support.service
 113ms systemd-tmpfiles-clean.service
 111ms console-setup.service
 104ms modprobe@configfs.service
  80ms alsa-restore.service
  79ms atopacct.service
  75ms systemd-timesyncd.service
  48ms systemd-update-utmp.service
  45ms proc-sys-fs-binfmt_misc.mount
  40ms systemd-user-sessions.service
  34ms dev-hugepages.mount
  33ms user-runtime-dir@1000.service$_systemd-analyze blame
3.583s dev-sdb1.device
2.870s systemd-journal-flush.service
1.984s NetworkManager.service
1.763s systemd-random-seed.service
1.672s nvidia-persistenced.service
1.621s systemd-modules-load.service
1.587s polkit.service
1.509s avahi-daemon.service
1.508s smartmontools.service
1.489s dhcpcd.service
1.436s systemd-logind.service
1.431s wpa_supplicant.service
1.065s tlp.service
 993ms systemd-udevd.service
 934ms apt-daily-upgrade.service
 768ms networking.service
 758ms rsyslog.service
 652ms lm-sensors.service
 584ms e2scrub_reap.service
 512ms keyboard-setup.service
 508ms user@1000.service
 443ms ModemManager.service
 442ms apparmor.service
 408ms systemd-tmpfiles-setup-dev.service
 256ms systemd-udev-trigger.service
 229ms systemd-journald.service
 216ms systemd-tmpfiles-setup.service
 181ms dev-disk-by\x2duuid-ee9858c7\x2d17a0\x2d4141\x2da2a9\x2d12c06e3b86af.swap
 179ms systemd-sysusers.service
 174ms modprobe@drm.service
 165ms modprobe@fuse.service
 149ms systemd-sysctl.service
 144ms media-sdX3.mount
 131ms ifupdown-pre.service
 124ms systemd-remount-fs.service
 119ms binfmt-support.service
 113ms systemd-tmpfiles-clean.service
 111ms console-setup.service
 104ms modprobe@configfs.service
  80ms alsa-restore.service
  79ms atopacct.service
  75ms systemd-timesyncd.service
  48ms systemd-update-utmp.service
  45ms proc-sys-fs-binfmt_misc.mount
  40ms systemd-user-sessions.service
  34ms dev-hugepages.mount
  33ms user-runtime-dir@1000.service

$_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 @7.965s
└─multi-user.target @7.965s
  └─ModemManager.service @7.521s +443ms
    └─polkit.service @5.931s +1.587s
      └─basic.target @5.878s
        └─sockets.target @5.878s
          └─uuidd.socket @5.878s
            └─sysinit.target @5.877s
              └─apparmor.service @5.434s +442ms
                └─local-fs.target @5.432s
                  └─media-sdX3.mount @5.287s +144ms
                    └─dev-sdb3.device @5.268s

$_systemd-analyze
Startup finished in 2.931s (kernel) + 9.034s (userspace) = 11.966s 
graphical.target reached after 7.965s in userspace
amd_amd ★★★★★
()

Случаем, монтированием несуществующих устройств при запуске ОС твоя не занимается?

speed_vm ★
()

systemd-journal-flush.service @7.730s +10.331s

что он у тебя флушит аж целых 10 секунд?

Minona ★★☆
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.
← flatpak разные версии одной и той же программы
Desktop
Автомонтирование разделов в i3 с помощью devmon+udevil →