我不知道如何让我的系统启动更快，在网上找不到有用的信息，因为我遵循了几乎所有的建议，但只是快了几秒钟。
我已启用休眠模式，为此我使用了大约 9GB 的交换内存空间（我的 RAM 是 8GB，据说建议至少与 RAM 内存一样大）我认为可能是启动参数（因为它需要检查一些 UUID 空间才能从休眠模式启动）导致了一些延迟。但在启动时删除这些参数并没有带来任何改善。我还发现从休眠模式启动并不需要花费太多时间（大约 7 到 10 秒）
最后我实现了 Windows 双启动，但我将 GRUB 设置为延迟 2 秒，我认为这样优化得很好。
输出如下 systemd-analyze critical-chain：
The time the unit took to start is printed after the "+" character.
graphical.target @1min 2.717s
└─multi-user.target @1min 2.717s
└─plymouth-quit-wait.service @22.707s +40.009s
└─systemd-user-sessions.service @22.596s +104ms
└─network.target @22.591s
└─NetworkManager.service @17.322s +5.266s
└─dbus.service @17.320s
└─basic.target @17.266s
└─sockets.target @17.266s
└─uuidd.socket @17.266s
└─sysinit.target @17.200s
└─systemd-update-utmp.service @16.854s +345ms
└─systemd-tmpfiles-setup.service @15.492s +1.324s
└─local-fs.target @15.451s
└─boot-efi.mount @15.373s +76ms
└─systemd-fsck@dev-disk-by\x2duuid-FCAE\x2d6336.service @14.164s +1.180s
└─dev-disk-by\x2duuid-FCAE\x2d6336.device @14.163s
输出如下 systemd-analyze blame：
40.009s plymouth-quit-wait.service
10.600s NetworkManager-wait-online.service
10.275s networkd-dispatcher.service
8.334s udisks2.service
7.877s accounts-daemon.service
7.818s cups.service
6.549s apache2.service
5.266s NetworkManager.service
4.612s dev-sda5.device
4.469s gdm.service
4.173s upower.service
3.990s fwupd.service
3.909s gpu-manager.service
3.639s avahi-daemon.service
3.638s bluetooth.service
3.602s polkit.service
3.138s switcheroo-control.service
3.125s thermald.service
3.119s systemd-logind.service
2.858s apport.service
2.804s wpa_supplicant.service
2.345s grub-common.service
1.812s packagekit.service
1.715s rsyslog.service
1.710s secureboot-db.service
1.689s ModemManager.service
1.511s e2scrub_reap.service
1.500s plymouth-start.service
1.329s update-notifier-download.service
1.324s systemd-tmpfiles-setup.service
1.316s apparmor.service
1.307s systemd-resolved.service
1.200s nvidia-persistenced.service
1.180s systemd-fsck@dev-disk-by\x2duuid-FCAE\x2d6336.service
1.028s systemd-modules-load.service
815ms systemd-sysusers.service
766ms systemd-random-seed.service
758ms keyboard-setup.service
682ms tlp.service
623ms systemd-journald.service
611ms systemd-udev-trigger.service
588ms [email protected]
572ms swapfile.swap
523ms kerneloops.service
485ms systemd-backlight@backlight:intel_backlight.service
449ms binfmt-support.service
414ms systemd-udevd.service
345ms systemd-update-utmp.service
305ms systemd-tmpfiles-setup-dev.service
297ms plymouth-read-write.service
296ms colord.service
287ms systemd-oomd.service
271ms [email protected]
266ms grub-initrd-fallback.service
259ms systemd-sysctl.service
256ms systemd-tmpfiles-clean.service
153ms systemd-timesyncd.service
151ms setvtrgb.service
137ms systemd-remount-fs.service
123ms [email protected]
115ms systemd-journal-flush.service
108ms console-setup.service
104ms systemd-user-sessions.service
96ms modprobe@chromeos_pstore.service
93ms ufw.service
76ms boot-efi.mount
63ms [email protected]
62ms [email protected]
48ms openvpn.service
43ms proc-sys-fs-binfmt_misc.mount
37ms geoclue.service
32ms dev-hugepages.mount
31ms dev-mqueue.mount
30ms sys-kernel-debug.mount
29ms sys-kernel-tracing.mount
26ms kmod-static-nodes.service
23ms rtkit-daemon.service
13ms alsa-restore.service
10ms modprobe@efi_pstore.service
8ms sys-fs-fuse-connections.mount
6ms sys-kernel-config.mount
5ms modprobe@pstore_blk.service
5ms [email protected]
4ms systemd-update-utmp-runlevel.service
2ms modprobe@pstore_zone.service
1ms [email protected]
和这里剧情
我将不胜感激任何能得到的帮助。我不知道该怎么做才能让它启动得更快，或者它是否已经足够快而我无法再加快速度了。