• Home
  • Categories
  • WIKI
  • LANGUAGE: en
    • whats your best bootup time systemd-analyze ?
    Community Discussion 1923 views · 19 replies ·
    Tofloor
    poster avatar
    amrith
    deepin
    2018-02-22 20:35
    Author
    please share your boot times use command:
    1. systemd-analyze
    Copy the Code
    and pls share if you are using other linux

    my boot time
    1. [amrith@archbox ~]$ systemd-analyze
    2. Startup finished in 7.863s (firmware) + 3.519s (loader) + 8.351s (kernel) + 17.788s (userspace) = 37.523s
    3. graphical.target reached after 11.943s in userspace
    Copy the Code


    Reply Favorite View the author
    All Replies
    Blogghete
    deepin
    2018-02-23 08:04
    #1
    Solus operating system:

    Startup finished in 1.525s (kernel) + 2.694s (initrd) + 32.035s (userspace) = 36.255s

    I will tell you the deepin startup statistics as soon as possible.
    Reply View the author
    bobo
    deepin
    2018-02-23 09:01
    #2
    Mine with ssd:

    2. $ systemd-analyze
    3. Startup finished in 3.827s (kernel) + 14.855s (userspace) = 18.683s
    Copy the Code

    Reply View the author
    Blogghete
    deepin
    2018-02-23 09:06
    #3
    deepin 15.5 64-bit operating system:

    Startup finished in 8.485s (kernel) + 34.205s (userspace) = 42.691s

    One thing to improve in deepin is the boot time without any doubt.



    Reply View the author
    meda
    deepin
    2018-02-23 22:46
    #4
    The result is with Samsung 850 Evo
    1. Startup finished in 4.287s (firmware) + 2.891s (loader) + 3.943s (kernel) + 3.033s (userspace) = 14.156s
    Copy the Code
    Reply View the author
    junmoxiao
    deepin
    2018-02-25 04:35
    #5
    2017 x1c
    1. junmoxiao@cat:~$ systemd-analyze
    2. Startup finished in 6.097s (firmware) + 2.876s (loader) + 4.366s (kernel) + 6.984s (userspace) = 20.325s
    Copy the Code
    Reply View the author
    robertsala
    deepin
    2018-02-27 06:53
    #6
    https://bbs.deepin.org/post/153446
    The result is with Samsung 850 Evo

    I got mine to boot up at 17 or 18 seconds. Have you been able to find out if someone has been able to install Samsung Magician? It has a feature called "RAPID MODE" to further maximize the speed. I have heard Windows users boot their pc's/laptops in 7 or 8 seconds. I also created a post in Deepin's appstore to see if they can work their magic!
    Reply View the author
    meda
    deepin
    2018-02-28 19:41
    #7
    Edited by meda at 2018-2-28 11:42

    you must check the running services
    1. systemd-analyze blame
    Copy the Code
    close needless services beside I tried RAPID MODE but I didn't see different by the way check the links Debian SSD    Systemd
    Reply View the author
    la******[email protected]
    deepin
    2018-02-28 20:10
    #8
    Antergos with Deepin Desktop Environment:
    1. Startup finished in 14.531s (firmware) + 2.497s (loader) + 12.006s (kernel) + 9.853s (userspace) = 38.888s
    2. graphical.target reached after 9.853s in userspace
    Copy the Code
    1.          36.553s updatedb.service
    2.           7.423s man-db.service
    3.           6.408s samba.service
    4.           4.322s ufw.service
    5.           3.928s lvm2-monitor.service
    6.           3.714s dev-sdb2.device
    7.           3.307s winbindd.service
    8.           2.048s systemd-journal-flush.service
    9.           2.046s udisks2.service
    10.           1.150s NetworkManager.service
    11.           1.089s smbd.service
    12.           1.005s ldconfig.service
    13.            925ms ModemManager.service
    14.            835ms systemd-udevd.service
    15.            724ms nmbd.service
    16.            671ms systemd-networkd.service
    17.            538ms systemd-sysusers.service
    18.            479ms systemd-tmpfiles-clean.service
    19.            452ms systemd-journal-catalog-update.service
    20.            439ms polkit.service
    21.            432ms upower.service
    22.            340ms systemd-tmpfiles-setup.service
    23.            296ms rtkit-daemon.service
    24.            284ms systemd-logind.service
    25.            282ms systemd-journald.service
    26.            279ms systemd-tmpfiles-setup-dev.service
    27.            201ms systemd-timesyncd.service
    28.            199ms lightdm.service
    29.            183ms systemd-udev-trigger.service
    30.            182ms systemd-resolved.service
    31.            178ms org.cups.cupsd.service
    32.            170ms systemd-binfmt.service
    33.            166ms boot-efi.mount
    34.            158ms accounts-daemon.service
    35.            152ms dev-mqueue.mount
    36.            151ms dev-hugepages.mount
    37.            150ms sys-kernel-debug.mount
    38.            149ms systemd-remount-fs.service
    39.            142ms systemd-user-sessions.service
    40.            137ms systemd-random-seed.service
    41.            136ms systemd-update-utmp.service
    42.            136ms home.mount
    43.            118ms tmp.mount
    44.            109ms logrotate.service
    45.             96ms avahi-daemon.service
    46.             69ms systemd-modules-load.service
    47.             56ms proc-sys-fs-binfmt_misc.mount
    48.             51ms [email protected]
    49.             43ms systemd-sysctl.service
    50.             33ms kmod-static-nodes.service
    51.             19ms alsa-restore.service
    52.              3ms systemd-update-done.service
    53.              1ms sys-fs-fuse-connections.mount
    54.              1ms sys-kernel-config.mount
    Copy the Code
    Reply View the author
    robertsala
    deepin
    2019-01-26 09:12
    #9
    Startup finished in 2.791s (firmware) + 1.563s (loader) + 3.577s (kernel) + 2.683s (userspace) = 10.615s
    graphical.target reached after 2.573s in userspace
    Reply View the author
    oscararg
    deepin
    2019-01-26 09:44
    #10
    That's from Elementary OS, using an Adata SP550 120GB SSD

    Startup finished in 4.364s (kernel) + 2.512s (userspace) = 6.877s
    graphical.target reached after 2.509s in userspace

    I remember loading Deepin in 10-20sec depending on configuration.
    Reply View the author
    jharbison
    deepin
    2019-02-01 05:24
    #11
    With SSD
    Startup finished in 2.732s (kernel) + 6.998s (userspace) = 9.731s
    graphical.target reached after 6.989s in userspace
    Reply View the author
    m***[email protected]
    deepin
    2019-02-01 13:18
    #12
    WIth SSD Drive:
    1. systemd-analyze
    2. Startup finished in 7.749s (firmware) + 16.060s (loader) + 3.806s (kernel) + 6.125s (userspace) = 33.740s
    3. graphical.target reached after 6.114s in userspace
    Copy the Code
    Reply View the author
    hiphile
    deepin
    2019-02-01 13:43
    #13
    RebornOS (Arch Linux) with the Deepin Desktop Environment - Samsung EVO 850 SSD

    1. systemd-analyze
    2. Startup finished in 2.475s (kernel) + 3.500s (userspace) = 5.975s
    3. graphical.target reached after 1.204s in userspace
    Copy the Code
    Reply View the author
    zh******[email protected]
    deepin
    2019-02-01 16:06
    #14
    本帖最后由 jeffcao 于 2019-2-1 08:08 编辑

    jeff@deepin:~$ systemd-analyze
    Startup finished in 20.499s (firmware) + 8.816s (loader) + 13.984s (kernel) + 8.456s (userspace) = 51.756s
    graphical.target reached after 7.179s in userspace

    我的也是Samsung EVO 850 SSD，为什么这么慢啊？
    jeff@deepin:~$ systemd-analyze blame
              4.498s NetworkManager-wait-online.service
              2.856s udisks2.service
              1.849s lvm2-monitor.service
               830ms plymouth-quit-wait.service
               806ms apt-daily.service
               581ms apt-daily-upgrade.service
               382ms dev-sda3.device
               373ms systemd-logind.service
               291ms NetworkManager.service
               191ms systemd-hwdb-update.service
               164ms laptop-mode.service
               157ms systemd-timesyncd.service
               151ms ModemManager.service
               139ms accounts-daemon.service
               133ms deepin-accounts-daemon.service
               130ms upower.service
               110ms lightdm.service
                92ms wpa_supplicant.service
                85ms systemd-journal-flush.service
                82ms smbd.service
                69ms systemd-udev-trigger.service
                51ms lastore-daemon.service
                50ms systemd-journald.service
                46ms [email protected]
                38ms networking.service
                31ms systemd-fsck@dev-disk-by\x2duuid-0DF7\x2d121C.service
                29ms nmbd.service
                26ms systemd-udevd.service
                25ms systemd-fsck-root.service
                16ms systemd-tmpfiles-setup.service
                15ms systemd-binfmt.service
                14ms plymouth-start.service

    14ms polkit.service
                12ms plymouth-read-write.service
                12ms systemd-modules-load.service
                12ms lmt-poll.service
                 9ms dev-hugepages.mount
                 9ms dev-mqueue.mount
                 9ms blk-availability.service
                 7ms systemd-update-utmp-runlevel.service
                 7ms systemd-sysusers.service
                 7ms systemd-remount-fs.service
                 6ms sys-kernel-debug.mount
                 6ms systemd-tmpfiles-setup-dev.service
                 6ms boot-efi.mount
                 5ms systemd-update-utmp.service
                 5ms proc-sys-fs-binfmt_misc.mount
                 5ms systemd-sysctl.service
                 5ms systemd-user-sessions.service
                 4ms kmod-static-nodes.service
                 4ms ifupdown-pre.service
                 3ms systemd-random-seed.service
                 3ms sys-kernel-config.mount
                 2ms sys-fs-fuse-connections.mount


    Reply View the author
    foxbcd
    deepin
    2019-02-01 16:32
    #15
    [tang@TM-1607 ~]$ systemd-analyze
    Startup finished in 2.998s (firmware) + 1.300s (loader) + 2.592s (kernel) + 1.946s (userspace) = 8.837s
    graphical.target reached after 1.404s in userspace

    Reply View the author
    s***[email protected]
    deepin
    2019-02-01 17:11
    #16
    Startup finished in 7.558s (kernel) + 1min 15.127s (userspace) = 1min 22.686s
    graphical.target reached after 49.162s in userspace
    Reply View the author
    HualetWang
    deepin
    2019-02-01 21:39
    #17
    https://bbs.deepin.org/post/153446
    Startup finished in 7.558s (kernel) + 1min 15.127s (userspace) = 1min 22.686s
    graphical.target reach ...

    Use a SSD, dude
    Reply View the author
    jsxlop
    deepin
    2019-02-02 08:31
    #18
    Deepin 15.9.1 desktop in virtualbox
    1. Startup finished in 7.788s (kernel) + 1min 2.228s (userspace) = 1min 10.017s
    2. graphical.target reached after 1min 2.192s in userspace
    Copy the Code
    Reply View the author
    Alex
    deepin
    2019-02-10 09:00
    #19
    Deepin 15.9.1 with SSD
    *Active Startup Delay in the Control Center - I do not know if this interferes with anything.

    Startup finished in 2.625s (firmware) + 4.410s (loader) + 4.946s (kernel) + 14.266s (userspace) = 26.249s
    graphical.target reached after 14.255s in userspace
    Reply View the author