• Home
  • Categories
  • WIKI
  • LANGUAGE: en
    • 好的，Nice！我们来看看为什么开机这么久！
    deepin Talks 6344 views · 57 replies ·
    Tofloor
    poster avatar
    dzuiuabi
    deepin
    2017-12-29 17:27
    Author
    没有滑稽很不习惯。

    2. ~$ systemd-analyze
    3. Startup finished in 8.193s (kernel) + 53.255s (userspace) = 1min 1.448s
    Copy the Code
    开了1分多钟，我觉得我可以在睡一会儿然后……
    然后在看看是什么东西这么拖后退。
    1. ~$ systemd-analyze blame
    2.          24.305s NetworkManager-wait-online.service
    3.           8.426s dev-sda8.device
    4.           6.966s ModemManager.service
    5.           6.621s nmbd.service
    6.           6.572s systemd-journal-flush.service
    7.           4.304s networking.service
    8.           4.301s smbd.service
    9.           3.954s accounts-daemon.service
    10.           2.965s NetworkManager.service
    11.           1.913s lightdm.service
    12.           1.823s avahi-daemon.service
    13.           1.775s systemd-logind.service
    14.           1.740s lvm2-monitor.service
    15.           1.696s keyboard-setup.service
    16.           1.552s systemd-binfmt.service
    17.           1.466s polkit.service
    18.           1.367s wpa_supplicant.service
    19.           1.362s lastore-daemon.service
    20.           1.333s systemd-backlight@backlight:acpi_video0.service
    21.           1.242s systemd-udevd.service
    22.           1.171s proc-sys-fs-binfmt_misc.mount
    23.           1.147s systemd-tmpfiles-setup.service
    24.           1.065s sys-kernel-debug.mount
    25.           1.035s dev-hugepages.mount
    26.            953ms systemd-modules-load.service
    Copy the Code
    哇呜~！第一次看见要启动这么长时间的服务，哇哦！抓住了一个大家伙！我在其他人晒出的开机时间和Blame也没看到NetworkManager-wait-online.service这个东西啊，怎么就占时间了嘛？

    于是我找了一些资料

    [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.

    意思就是这个服务必须要这样启动？网络服务，总而言之，很糟糕，我可能是这个论坛开机醉酒的用户

    Reply Favorite View the author
    All Replies
    1 / 3
    To page
    avatar
    dzuiuabi
    deepin
    2017-12-29 17:28
    #1
    所以有没有大虾帮我分析分析我的都是些什么服务
    Reply View the author
    avatar
    海天鹰
    deepin
    2017-12-29 17:52
    #2
    https://askubuntu.com/questions/ ... r-causing-slow-boot
    我开机50秒。
             20.216s mysql.service
             17.209s plymouth-quit-wait.service
             16.040s NetworkManager-wait-online.service
             14.430s networking.service
             10.168s apache2.service
              8.331s systemd-journal-flush.service
              7.527s ModemManager.service
              6.585s dev-sda8.device
              4.826s accounts-daemon.service
              4.394s systemd-logind.service
              4.392s gdomap.service
              4.335s avahi-daemon.service
              3.784s pppd-dns.service
              3.121s nmbd.service
              2.755s lightdm.service
              2.201s NetworkManager.service
              1.406s lvm2-monitor.service
              1.250s exim4.service
              1.149s systemd-tmpfiles-setup.service
              1.012s polkit.service
               959ms miredo.service
               896ms systemd-udevd.service
               847ms smbd.service
               827ms lastore-daemon.service
               742ms systemd-modules-load.service
               723ms systemd-tmpfiles-setup-dev.service
               630ms https://bbs.deepin.org/module
               472ms packagekit.service
               451ms plymouth-start.service
               448ms systemd-udev-trigger.service
               427ms systemd-timesyncd.service
               390ms systemd-user-sessions.service
               373ms systemd-binfmt.service
               331ms binfmt-support.service
               288ms upower.service
               269ms systemd-journald.service
               252ms systemd-tmpfiles-clean.service
               239ms udisks2.service
               236ms systemd-update-utmp.service
               213ms plymouth-read-write.service
               213ms systemd-random-seed.service
               205ms dev-hugepages.mount
               204ms sys-kernel-debug.mount
               203ms dev-mqueue.mount
               201ms proc-sys-fs-binfmt_misc.mount
               190ms swapfile.swap
               140ms mldonkey-server.service
               125ms kmod-static-nodes.service
               123ms systemd-sysctl.service
                93ms hostapd.service
                35ms systemd-remount-fs.service
                28ms alsa-restore.service
                 4ms systemd-update-utmp-runlevel.service
                 2ms sys-fs-fuse-connections.mount
    Reply View the author
    avatar
    152******22
    deepin
    2017-12-29 18:36
    #3
    amor@amor-PC:~$ systemd-analyze
    Startup finished in 3.315s (firmware) + 7.325s (loader) + 6.407s (kernel) + 57.673s (userspace) = 1min 14.721s
    amor@amor-PC:~$ systemd-analyze blame
             42.929s apt-daily.service
             25.434s docker.service
             17.017s plymouth-quit-wait.service
             14.476s alsa-restore.service
             13.472s dev-sdb3.device
             13.376s NetworkManager-wait-online.service
             11.787s networking.service
             10.154s nmbd.service
              8.528s teamviewerd.service
              8.426s virtualbox.service
              5.478s accounts-daemon.service
              4.690s systemd-logind.service
              4.597s pppd-dns.service
              4.423s smbd.service
              4.165s php7.1-fpm.service
              4.031s ModemManager.service
              3.696s udisks2.service
              3.486s wpa_supplicant.service
              3.384s systemd-journal-flush.service
              3.159s NetworkManager.service
              2.435s lightdm.service
              2.349s lastore-daemon.service
              2.221s lvm2-monitor.service
              2.028s systemd-user-sessions.service
              1.805s keyboard-setup.service
              1.644s systemd-binfmt.service
              1.453s dev-hugepages.mount
              1.452s sys-kernel-debug.mount
              1.450s dev-mqueue.mount
              1.333s systemd-udevd.service
              1.295s proc-sys-fs-binfmt_misc.mount
              1.222s systemd-tmpfiles-setup-dev.service
              1.107s systemd-modules-load.service
              1.016s binfmt-support.service
              1.015s plymouth-read-write.service
    Reply View the author
    avatar
    dzuiuabi
    deepin
    2017-12-29 18:42
    #4
    https://bbs.deepin.org/post/150831
    https://askubuntu.com/questions/ ... r-causing-slow-boot
    我开机50秒。
             20.216s mysql.service ...

    我昨天和你一样，但是今天就不一样了。
    Reply View the author
    avatar
    dzuiuabi
    deepin
    2017-12-29 18:44
    #5
    https://bbs.deepin.org/post/150831
    amor@amor-PC:~$ systemd-analyze
    Startup finished in 3.315s (firmware) + 7.325s (loader) + 6.407s (ke ...

    原来你是一个隐藏的醉酒的人
    Reply View the author
    avatar
    dzuiuabi
    deepin
    2017-12-29 18:45
    #6
    https://bbs.deepin.org/post/150831
    https://askubuntu.com/questions/ ... r-causing-slow-boot
    我开机50秒。
             20.216s mysql.service ...

    我如果systemctl disable NetworkManager-wait-online.service，禁用这个服务会用什么问题吗？
    Reply View the author
    avatar
    fliclumsy
    deepin
    2017-12-29 18:46
    #7
    本帖最后由 fliclumsy 于 2017-12-29 10:49 编辑

    Startup finished in 5.944s (kernel) + 24.448s (userspace) = 30.393s
    12.810s plymouth-quit-wait.service
              8.769s NetworkManager-wait-online.service
              5.442s apt-daily.service
              5.433s systemd-journal-flush.service
              4.408s dev-sda3.device
              3.639s nmbd.service
              2.676s ModemManager.service
              1.959s networking.service
              1.943s accounts-daemon.service
              1.942s vboxdrv.service
              1.300s NetworkManager.service
              1.264s pppd-dns.service
              1.117s lvm2-monitor.service
              1.068s lightdm.service
              1.019s avahi-daemon.service
               916ms wpa_supplicant.service
               802ms smbd.service
               788ms lastore-daemon.service
               763ms polkit.service
               672ms systemd-udevd.service
               604ms systemd-binfmt.service
               579ms dev-mqueue.mount
               569ms proc-sys-fs-binfmt_misc.mount
               528ms dev-hugepages.mount
               526ms sys-kernel-debug.mount
               512ms systemd-modules-load.service
               448ms miracle-dispd.service


    公司的垃圾一体机，win开机我已经尽量优化也要1分钟左右，所以我已经很满足了
    Reply View the author
    avatar
    dzuiuabi
    deepin
    2017-12-29 18:47
    #8
    https://bbs.deepin.org/post/150831
    Startup finished in 5.944s (kernel) + 24.448s (userspace) = 30.393s

    公司的垃圾一体机，win开机我已经 ...

    Windows我开机不用很久。没Deepin久
    Reply View the author
    avatar
    4***8@qq.com
    deepin
    2017-12-29 18:55
    #9
    去年刚换了ssd时，感觉真的快，有钱的话还是推荐ssd的。
    Reply View the author
    avatar
    fliclumsy
    deepin
    2017-12-29 19:02
    #10
    12.810s plymouth-quit-wait.service
    这个服务耗时最长，所以我就关闭了。。。
    但实际的效果只提高了不到1秒，而且感官上的开机实际更长了

    Startup finished in 5.967s (kernel) + 23.956s (userspace) = 29.923s
    Reply View the author
    avatar
    dzuiuabi
    deepin
    2017-12-29 19:06
    #11
    https://bbs.deepin.org/post/150831
    12.810s plymouth-quit-wait.service
    这个服务耗时最长，所以我就关闭了。。。
    但实际的效果只提高了不到1 ...

    我也觉得
    Reply View the author
    avatar
    dzuiuabi
    deepin
    2017-12-29 19:06
    #12
    https://bbs.deepin.org/post/150831
    去年刚换了ssd时，感觉真的快，有钱的话还是推荐ssd的。

    恩，我知道，毕竟是SSd
    Reply View the author
    avatar
    t1st
    deepin
    2017-12-29 19:39
    #13
    https://bbs.deepin.org/post/150831
    Startup finished in 5.944s (kernel) + 24.448s (userspace) = 30.393s
    12.810s plymouth-quit-wait.serv ...

    跟我差不多,
    Reply View the author
    avatar
    t1st
    deepin
    2017-12-29 19:41
    #14
    https://bbs.deepin.org/post/150831
    12.810s plymouth-quit-wait.service
    这个服务耗时最长，所以我就关闭了。。。
    但实际的效果只提高了不到1 ...

    应该是并行启动的吧,,,你把时间加在一起也不对啊
    Reply View the author
    avatar
    justforlxz
    deepin
    2017-12-29 19:44
    #15
    1. $ systemd-analyze
    2. Startup finished in 6.264s (kernel) + 16.013s (userspace) = 22.278s

    4. $ systemd-analyze blame
    5.           5.774s exim4.service
    6.           5.505s NetworkManager-wait-online.service
    7.           3.586s docker.service
    8.           3.272s home.mount
    9.           1.903s vmware.service
    10.           1.443s plymouth-quit-wait.service
    11.            542ms redis-server.service
    12.            537ms vmware-workstation-server.service
    13.            536ms lwsmd.service
    14.            424ms keyboard-setup.service
    15.            392ms lightdm.service
    16.            287ms dev-sda2.device
    17.            253ms nmbd.service
    18.            223ms teamviewerd.service
    19.            182ms systemd-timesyncd.service
    20.            178ms user@1000.service
    21.            151ms vmware-USBArbitrator.service
    22.            123ms ModemManager.service
    23.            120ms lvm2-monitor.service
    24.             98ms wpa_supplicant.service
    25.             91ms systemd-fsck@dev-disk-by\x2duuid-efb24e9f\x2d03f2\x2d4910\x2da9ea\x2d70ac713b062e.service
    26.             82ms networking.service
    27.             68ms NetworkManager.service
    28.             64ms smbd.service
    29.             59ms lastore-daemon.service
    30.             59ms dev-zram0.swap
    31.             57ms accounts-daemon.service
    32.             55ms bluetooth.service
    33.             53ms systemd-journal-flush.service
    34.             50ms systemd-tmpfiles-setup.service
    35.             47ms binfmt-support.service
    36.             46ms var-lib-docker.mount
    37.             45ms systemd-udev-trigger.service
    38.             42ms upower.service
    39.             41ms systemd-journald.service
    40.             38ms polkit.service
    41.             38ms systemd-fsck@dev-disk-by\x2duuid-7D73\x2dF83A.service
    42.             35ms systemd-binfmt.service
    43.             34ms udisks2.service
    44.             31ms systemd-udevd.service
    45.             31ms systemd-modules-load.service
    46.             28ms dev-hugepages.mount
    47.             25ms sys-kernel-debug.mount
    Copy the Code


    Reply View the author
    avatar
    要讲武德
    deepin
    2017-12-29 19:54
    #16
    1. Startup finished in 8.501s (firmware) + 6.817s (loader) + 2.574s (kernel) + 10.585s (userspace) = 28.479s
    Copy the Code

    1. systemd-analyze blame
    2.           5.809s NetworkManager-wait-online.service
    3.           2.677s vmware.service
    4.           1.164s vmware-workstation-server.service
    5.            931ms apt-daily.service
    6.            913ms nmbd.service
    7.            318ms dev-sda1.device
    8.            308ms smbd.service
    9.            305ms vmware-USBArbitrator.service
    10.            298ms geoclue.service
    11.            287ms lightdm.service
    12.            284ms plymouth-quit-wait.service
    13.            241ms ModemManager.service
    14.            153ms upower.service
    15.            147ms NetworkManager.service
    16.            111ms networking.service
    17.            104ms virtualbox.service
    18.            103ms plymouth-read-write.service
    19.            101ms lastore-daemon.service
    20.            101ms systemd-timesyncd.service
    21.             94ms systemd-journal-flush.service
    22.             71ms systemd-fsck@dev-disk-by\x2duuid-e331c0cf\x2d12fb\x2d44a4\x2d9dbc\x2d3d2518fe6130.service
    23.             65ms systemd-udevd.service
    24.             57ms systemd-modules-load.service
    25.             50ms lvm2-monitor.service
    26.             50ms accounts-daemon.service
    27.             49ms systemd-fsck@dev-disk-by\x2duuid-7554\x2dECE5.service
    28.             48ms user@1000.service
    29.             46ms systemd-journald.service
    30.             43ms systemd-udev-trigger.service
    31.             40ms polkit.service
    32.             35ms plymouth-start.service
    Copy the Code
    Reply View the author
    avatar
    海天鹰
    deepin
    2017-12-29 20:20
    #17
    https://bbs.deepin.org/post/150831
    12.810s plymouth-quit-wait.service
    这个服务耗时最长，所以我就关闭了。。。
    但实际的效果只提高了不到1 ...

    如何关闭服务？
    Reply View the author
    avatar
    rekols
    deepin
    2017-12-29 20:44
    #18
    1. Startup finished in 4.106s (kernel) + 6.850s (userspace) = 10.956s
    Copy the Code


    还有谁
    Reply View the author
    avatar
    rekols
    deepin
    2017-12-29 20:46
    #19
    1. $ systemd-analyze blame
    2.           6.224s NetworkManager-wait-online.service
    3.           1.500s plymouth-quit-wait.service
    4.            333ms lightdm.service
    5.            270ms dev-nvme0n1p5.device
    6.            164ms loadcpufreq.service
    7.            145ms systemd-timesyncd.service
    8.            100ms ModemManager.service
    9.             93ms networking.service
    10.             83ms systemd-modules-load.service
    11.             78ms upower.service
    12.             76ms systemd-udev-trigger.service
    13.             74ms NetworkManager.service
    14.             68ms accounts-daemon.service
    15.             61ms smbd.service
    16.             58ms lastore-daemon.service
    17.             54ms nmbd.service
    18.             50ms systemd-udevd.service
    19.             50ms systemd-journald.service
    20.             49ms systemd-journal-flush.service
    21.             39ms lvm2-monitor.service
    22.             32ms bluetooth.service
    23.             25ms polkit.service
    24.             24ms systemd-logind.service
    25.             22ms avahi-daemon.service
    26.             22ms user@1000.service
    27.             20ms systemd-tmpfiles-setup-dev.service
    28.             19ms systemd-tmpfiles-setup.service
    29.             18ms plymouth-read-write.service
    30.             18ms systemd-binfmt.service
    31.             18ms systemd-rfkill.service
    32.             17ms plymouth-start.service
    33.             16ms binfmt-support.service
    34.             15ms pppd-dns.service
    35.             15ms systemd-tmpfiles-clean.service
    36.             14ms wpa_supplicant.service
    37.             14ms udisks2.service
    38.             13ms systemd-sysctl.service
    39.             13ms cpufrequtils.service
    40.             11ms systemd-remount-fs.service
    41.             11ms dev-mqueue.mount
    42.             11ms miracle-dispd.service
    43.             10ms sys-kernel-debug.mount
    44.             10ms kmod-static-nodes.service
    45.             10ms sys-fs-fuse-connections.mount
    46.              9ms dev-hugepages.mount
    47.              9ms systemd-user-sessions.service
    48.              8ms systemd-update-utmp.service
    49.              7ms systemd-random-seed.service
    50.              7ms proc-sys-fs-binfmt_misc.mount
    51.              5ms systemd-backlight@backlight:intel_backlight.service
    52.              5ms miracle-wifid.service
    53.              4ms systemd-update-utmp-runlevel.service
    54.              3ms hostapd.service
    Copy the Code
    Reply View the author
    avatar
    bnbvb
    deepin
    2017-12-29 20:46
    #20
    1. Startup finished in 4.313s (kernel) + 5.432s (userspace) = 9.746s
    Copy the Code
    Reply View the author
    1 / 3
    To page