中文 
doooooit
deepin
2017-12-29 21:00 deepin 本帖最后由 shangxke 于 2017-12-29 13:02 编辑
SSD，NetworkManager 直接占了一半的时间
Copy the Code
SSD，NetworkManager 直接占了一半的时间
- ~$ systemd-analyze
- Startup finished in 5.192s (kernel) + 8.924s (userspace) = 14.117s
- ~$ systemd-analyze blame
- 7.740s NetworkManager-wait-online.service
- 1.537s plymouth-quit-wait.service
- 1.068s mysql.service
- 854ms apt-daily.service
- 414ms dev-sdb1.device
- 341ms lightdm.service
- 236ms upower.service
- 184ms exim4.service
- 137ms systemd-timesyncd.service
- 114ms systemd-rfkill.service
- 112ms ModemManager.service
- 102ms systemd-journal-flush.service
- 99ms systemd-udev-trigger.service
- 98ms networking.service
- 96ms NetworkManager.service
- 95ms smbd.service
- 87ms plymouth-read-write.service
- 83ms nmbd.service
- 73ms user@1000.service
- 72ms lastore-daemon.service
- 68ms accounts-daemon.service
- 58ms bluetooth.service
- 58ms systemd-journald.service
- 53ms systemd-fsck@dev-disk-by\x2duuid-5AC4\x2dFB0C.service
- 46ms ssh.service
- 43ms systemd-udevd.service
- 42ms lvm2-monitor.service
- 39ms gdomap.service
- 36ms systemd-fsck@dev-disk-by\x2duuid-5e41451e\x2d9fd2\x2d4fa7\x2da0af\x2ddf0b505644f3.service
- 36ms plymouth-start.service
- 30ms systemd-modules-load.service
- 29ms polkit.service
- 25ms systemd-tmpfiles-setup.service
- 24ms udisks2.service
- 21ms systemd-tmpfiles-setup-dev.service
- 20ms systemd-tmpfiles-clean.service
- 18ms avahi-daemon.service
- 18ms systemd-logind.service
- 17ms wpa_supplicant.service
- 17ms home.mount
- 13ms virtualbox.service
- 13ms boot-efi.mount
- 13ms dev-mqueue.mount
- 13ms systemd-binfmt.service
- 12ms dev-hugepages.mount
- 11ms alsa-restore.service
- 11ms miracle-wifid.service
- 11ms miracle-dispd.service
- 10ms systemd-update-utmp-runlevel.service
- 9ms dev-disk-by\x2duuid-194c193f\x2d3dbc\x2d4787\x2d8d71\x2db7f378661252.swap
- 9ms systemd-remount-fs.service
- 9ms kmod-static-nodes.service
- 8ms systemd-user-sessions.service
- 7ms systemd-update-utmp.service
- 7ms systemd-backlight@backlight:intel_backlight.service
- 5ms sys-kernel-debug.mount
- 5ms proc-sys-fs-binfmt_misc.mount
- 5ms pppd-dns.service
- 4ms systemd-sysctl.service
- 4ms systemd-random-seed.service
- 3ms sys-fs-fuse-connections.mount
Reply Like 0 View the author
我好像也感觉到了15.4的魅力
Looking Deepin ci 25.2.0 Developer/Unstable repositories 
然后在看看是什么东西这么拖后退。
于是我找了一些资料
[page]
[size=13.3333px]Hi
[size=13.3333px]I see
[size=13.3333px]Code:
7.872s NetworkManager-wait-online.service
[size=13.3333px]when I run a
[size=13.3333px]Code:
systemd-analyze blame
[size=13.3333px]Is this normal?
[size=13.3333px]Seems like it is adding a LOT of time to my boot.
[size=13.3333px]Any way to optimize?
[size=13.3333px]Centos 7 + MATE install
[size=13.3333px]
[size=13.3333px]有人就回复了：
Nope.
the problem is that systemd assumes the network is ready for use as soon as it starts NetworkManager.
When this is the case, nearly all network dependent actions fail - from network based filesystems, name lookups, time synchronization, databases, network user identifications (LDAP/NIS/...).
So much fails that the systemd developers had to start modifying a ton of other applications (this one being NetworkManager).
NetworkManager-wait-online is required to delay until the network is usable. This required modification of NetworkManager to explicitly send a "ready" signal back to systemd. This normally works (DHCP clients got modified too). And even the database servers got modified for the same reason.
This is one of the reasons systemd is considered a poor design, and imposes a LOT of things on services.
意思就是这个服务必须要这样启动？网络服务，总而言之，很糟糕，我可能是这个论坛开机醉酒的用户