大家开机都需要多长时间?
Tofloor
poster avatar
SamLukeYes
deepin
2020-12-08 03:24
Author

一起来用 systemd-analyze 秀一下开机时间吧[开心]


Reply Favorite View the author
All Replies
1 / 2
To page
caoayu
deepin
2020-12-08 03:34
#1

比较慢

Reply View the author
mdd3135
deepin
2020-12-08 03:51
#2

你是怎么做到这么快的启动的?

Reply View the author
SamLukeYes
deepin
2020-12-08 03:56
#3
mdd3135

你是怎么做到这么快的启动的?

我直接用 uefi 启动内核,所以 loader 是毫秒级。内核是 linux-surface,没有装任何 dkms。图形界面是 gdm + gnome (wayland)[尾]

Reply View the author
zwq133
deepin
2020-12-08 04:15
#4



2个字符

Reply View the author
liulangdedao
deepin
2020-12-08 04:40
#5

系统是从15系统升到15.11,然后在到20,用的机械盘,装了一堆的软件,然后开机就是目前这个样子……不过我对开机速度无所谓,因为我的win下开机也是这个样,只要使用起来流畅就可以了。

Reply View the author
Fredoong
deepin
2020-12-08 05:25
#6


我用的是一块2009年生产的320G希捷机械硬盘,就问你怕不怕。

Reply View the author
残念
deepin
2020-12-08 05:29
#7

放飞自我的状态[怀疑]

Reply View the author
SamLukeYes
deepin
2020-12-08 05:47
#8
Fredoong


我用的是一块2009年生产的320G希捷机械硬盘,就问你怕不怕。

确认过眼神,是用 MBR 的老古董了[开心]

Reply View the author
yty
deepin
2020-12-08 06:14
#9


我的也是老硬盘了,150G

Reply View the author
神末shenmo
deepin
Spark-App
Q&A Team
2020-12-08 06:16
#10
12.125s plymouth-quit-wait.service
7.459s udisks2.service
6.843s deepin-accounts-daemon.service
5.973s systemd-journal-flush.service
5.851s ModemManager.service
5.846s NetworkManager-wait-online.service
5.544s man-db.service
5.285s laptop-mode.service
4.752s accounts-daemon.service
3.735s plymouth-read-write.service
3.118s rsyslog.service
3.117s NetworkManager.service
3.117s logrotate.service
3.112s wpa_supplicant.service
3.046s pppd-dns.service
2.980s alsa-restore.service
2.868s apt-daily.service
2.739s lastore-daemon.service
2.629s dev-sda5.device
2.526s smbd.service
2.484s systemd-fsck@dev-disk-by\x2duuid-34c4f5cb\x2dda53\x2d4e2d\x2da468\x2dbb3af5adb173.service
2.435s nmbd.service
2.333s networking.service
1.991s ssh.service
1.675s systemd-fsck@dev-disk-by\x2duuid-fb3de21c\x2d4f7a\x2d4b5e\x2dbef5\x2d2df163891939.service
1.621s deepin-anything-tool.service
1.145s lightdm.service
935ms apt-daily-upgrade.service
904ms systemd-hwdb-update.service
843ms systemd-fsck@dev-disk-by\x2duuid-e352c00c\x2d8f63\x2d4b8e\x2dae47\x2dc7e5f2f8e60e.service
735ms polkit.service
599ms user@1000.service
581ms systemd-logind.service
556ms upower.service
519ms data.mount
470ms deepin-login-sound.service
445ms lmt-poll.service
417ms systemd-modules-load.service
408ms binfmt-support.service
358ms systemd-udev-trigger.service
345ms systemd-tmpfiles-clean.service
334ms opt.mount
285ms systemd-binfmt.service
284ms recovery.mount
280ms systemd-sysusers.service
270ms systemd-user-sessions.service
256ms kmod-static-nodes.service
252ms systemd-journald.service
243ms dde-filemanager-daemon.service
238ms systemd-tmpfiles-setup-dev.service
227ms systemd-tmpfiles-setup.service
226ms systemd-random-seed.service
219ms proc-sys-fs-binfmt_misc.mount
210ms boot.mount
204ms systemd-remount-fs.service
204ms systemd-udevd.service
203ms lvm2-monitor.service
157ms systemd-sysctl.service
127ms dev-disk-by\x2duuid-72b832de\x2dbf0d\x2d4cd1\x2db199\x2db215d72efd1a.swap
118ms ifupdown-pre.service
108ms systemd-timesyncd.service
98ms home.mount
96ms blk-availability.service
90ms systemd-update-utmp.service
58ms root.mount
57ms plymouth-start.service
48ms dev-mqueue.mount
21ms dev-hugepages.mount
20ms user-runtime-dir@1000.service
19ms sys-kernel-debug.mount
10ms systemd-update-utmp-runlevel.service
7ms var.mount
4ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount
sy120zx@sy120zx-PC:~$  systemd-analyze
Startup finished in 6.439s (kernel) + 29.635s (userspace) = 36.075s
graphical.target reached after 29.622s in userspace

一个机械 2011年学校机房
小伙子不要对Legacy+MBR有偏见,至少deepin to go一定要这么做,因为兼容性好,而且也不是特别慢


Reply View the author
SamLukeYes
deepin
2020-12-08 06:42
#11
神末shenmo
12.125s plymouth-quit-wait.service
7.459s udisks2.service
6.843s deepin-accounts-daemon.service
5.973s systemd-journal-flush.service
5.851s ModemManager.service
5.846s NetworkManager-wait-online.service
5.544s man-db.service
5.285s laptop-mode.service
4.752s accounts-daemon.service
3.735s plymouth-read-write.service
3.118s rsyslog.service
3.117s NetworkManager.service
3.117s logrotate.service
3.112s wpa_supplicant.service
3.046s pppd-dns.service
2.980s alsa-restore.service
2.868s apt-daily.service
2.739s lastore-daemon.service
2.629s dev-sda5.device
2.526s smbd.service
2.484s systemd-fsck@dev-disk-by\x2duuid-34c4f5cb\x2dda53\x2d4e2d\x2da468\x2dbb3af5adb173.service
2.435s nmbd.service
2.333s networking.service
1.991s ssh.service
1.675s systemd-fsck@dev-disk-by\x2duuid-fb3de21c\x2d4f7a\x2d4b5e\x2dbef5\x2d2df163891939.service
1.621s deepin-anything-tool.service
1.145s lightdm.service
935ms apt-daily-upgrade.service
904ms systemd-hwdb-update.service
843ms systemd-fsck@dev-disk-by\x2duuid-e352c00c\x2d8f63\x2d4b8e\x2dae47\x2dc7e5f2f8e60e.service
735ms polkit.service
599ms user@1000.service
581ms systemd-logind.service
556ms upower.service
519ms data.mount
470ms deepin-login-sound.service
445ms lmt-poll.service
417ms systemd-modules-load.service
408ms binfmt-support.service
358ms systemd-udev-trigger.service
345ms systemd-tmpfiles-clean.service
334ms opt.mount
285ms systemd-binfmt.service
284ms recovery.mount
280ms systemd-sysusers.service
270ms systemd-user-sessions.service
256ms kmod-static-nodes.service
252ms systemd-journald.service
243ms dde-filemanager-daemon.service
238ms systemd-tmpfiles-setup-dev.service
227ms systemd-tmpfiles-setup.service
226ms systemd-random-seed.service
219ms proc-sys-fs-binfmt_misc.mount
210ms boot.mount
204ms systemd-remount-fs.service
204ms systemd-udevd.service
203ms lvm2-monitor.service
157ms systemd-sysctl.service
127ms dev-disk-by\x2duuid-72b832de\x2dbf0d\x2d4cd1\x2db199\x2db215d72efd1a.swap
118ms ifupdown-pre.service
108ms systemd-timesyncd.service
98ms home.mount
96ms blk-availability.service
90ms systemd-update-utmp.service
58ms root.mount
57ms plymouth-start.service
48ms dev-mqueue.mount
21ms dev-hugepages.mount
20ms user-runtime-dir@1000.service
19ms sys-kernel-debug.mount
10ms systemd-update-utmp-runlevel.service
7ms var.mount
4ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount
sy120zx@sy120zx-PC:~$  systemd-analyze
Startup finished in 6.439s (kernel) + 29.635s (userspace) = 36.075s
graphical.target reached after 29.622s in userspace

一个机械 2011年学校机房
小伙子不要对Legacy+MBR有偏见,至少deepin to go一定要这么做,因为兼容性好,而且也不是特别慢


启动盘一般做成 UEFI 和 MBR 都支持的比较好吧。我以前用的上网本只支持 MBR,现在用的苏菲只支持 UEFI[尾]

Reply View the author
solothink
deepin
2020-12-08 16:09
#12
Fredoong


我用的是一块2009年生产的320G希捷机械硬盘,就问你怕不怕。

这么厉害啊!我是固态硬盘,但是Startup finished in 3.645s (kernel) + 1min 7.764s (userspace) = 1min 11.410s 

graphical.target reached after 1min 7.757s in userspace



Reply View the author
蒙笛
deepin
2020-12-08 17:03
#13

,2013年老笔记本,cpui5-3230,后来加了内存,换了固态硬盘。

Reply View the author
梁山伯住阳台
deepin
2020-12-08 17:32
#14

Startup finished in 6.618s (firmware) + 7.643s (loader) + 3.758s (kernel) + 28.029s (userspace) = 46.049s
graphical.target reached after 27.947s in userspace

Reply View the author
梁山伯住阳台
deepin
2020-12-08 17:34
#15
Fredoong


我用的是一块2009年生产的320G希捷机械硬盘,就问你怕不怕。

我的比你快一丢丢[开心]

Reply View the author
angelworkgroup
deepin
2020-12-08 17:56
#16

alex@alex-PC:~$ systemd-analyze
Startup finished in 7.013s (kernel) + 30.446s (userspace) = 37.460s
graphical.target reached after 30.407s in userspace
alex@alex-PC:~$ 


我这老机器啊。[污]

Reply View the author
KeiSyut
deepin
2020-12-08 18:44
#17

还行吧。老机子的了。

Reply View the author
神末shenmo
deepin
Spark-App
Q&A Team
2020-12-08 19:04
#18
SamLukeYes

启动盘一般做成 UEFI 和 MBR 都支持的比较好吧。我以前用的上网本只支持 MBR,现在用的苏菲只支持 UEFI[尾]

How?

Reply View the author
184******79
deepin
2020-12-08 19:09
#19

deepin在机械硬盘,启动1分半,win用的固态,启动10s

Reply View the author
SamLukeYes
deepin
2020-12-08 19:11
#20
神末shenmo

How?

ventoy 应该是同时支持 MBR 和 UEFI 的吧[困惑]

Reply View the author
1 / 2
To page