من از فدورا ۳۳ استفاده میکنم و سرعت لودش به نسبت اینکه از هارد ssd استفاده میکنم خیلی پایینه حدود ۱ دقیقه نیم زمان بوت سیستم هست که از دید من خیلی زیاده طی بررسی با دستور زیر
کد: انتخاب همه
-> $ systemd-analyze
Startup finished in 5.837s (firmware) + 2.574s (loader) + 1.768s (kernel) + 4.177s (initrd) + 1min 6.746s (userspace) = 1min 21.105s
graphical.target reached after 1min 6.338s in userspace
کد: انتخاب همه
-> $ systemd-analyze blame
58.585s akmods.service >
49.870s plymouth-quit-wait.service >
11.324s NetworkManager-wait-online.service >
2.991s upower.service >
2.761s tor@obfs4.service >
2.407s udisks2.service >
1.803s firewalld.service >
1.782s ModemManager.service >
1.773s avahi-daemon.service >
1.756s abrtd.service >
1.697s rtkit-daemon.service >
1.681s switcheroo-control.service >
1.658s sssd.service >
1.640s systemd-homed.service >
1.636s thermald.service >
1.409s dracut-initqueue.service >
1.197s lvm2-monitor.service >
931ms fwupd.service >
875ms plymouth-switch-root.service >
869ms initrd-switch-root.service >
669ms systemd-resolved.service >
549ms accounts-daemon.service >
526ms polkit.service >
516ms systemd-logind.service >
413ms initrd-parse-etc.service >
402ms tlp.service >
281ms user@1000.service >
277ms NetworkManager.service >
262ms bluetooth.service >
261ms systemd-vconsole-setup.service >
259ms import-state.service >
233ms systemd-udevd.service >
215ms systemd-journal-flush.service >
200ms systemd-udev-trigger.service >
190ms systemd-tmpfiles-setup.service >
185ms cups.service >
163ms var-lib-nfs-rpc_pipefs.mount >
162ms livesys.service >
161ms auditd.service >
157ms gssproxy.service >
150ms sssd-kcm.service >
149ms dbus-broker.service >
135ms packagekit.service >
130ms iscsi-shutdown.service >
116ms systemd-fsck@dev-disk-by\x2duuid-194ffa68\x2d5f90\x2d47c5\x2da470\x2d7c>
109ms dracut-cmdline.service >
109ms dracut-pre-pivot.service >
102ms chronyd.service >
95ms systemd-journald.service >
94ms livesys-late.service >
92ms sysroot.mount >
76ms systemd-fsck@dev-disk-by\x2duuid-6E42\x2d0D31.service >
74ms systemd-userdbd.service >
70ms systemd-tmpfiles-setup-dev.service >
66ms dracut-pre-udev.service >
61ms initrd-cleanup.service >
59ms swap-create@zram0.service >
52ms boot.mount >
52ms colord.service >
52ms vboxdrv.service >
47ms systemd-user-sessions.service >
46ms flatpak-system-helper.service >
45ms dev-mqueue.mount >
44ms systemd-remount-fs.service >
43ms sys-kernel-debug.mount >
42ms dev-hugepages.mount >
41ms kmod-static-nodes.service >
41ms boot-efi.mount >
39ms nfs-convert.service >
39ms uresourced.service >
37ms systemd-update-utmp.service >
37ms dev-zram0.swap >
35ms gdm.service >
35ms user-runtime-dir@1000.service >
34ms systemd-fsck-root.service >
34ms wpa_supplicant.service >
33ms systemd-random-seed.service >
30ms modprobe@drm.service >
30ms plymouth-read-write.service >
26ms systemd-update-utmp-runlevel.service >
23ms systemd-sysctl.service >
21ms systemd-backlight@backlight:intel_backlight.service >
19ms plymouth-start.service >
18ms dracut-shutdown.service >
14ms home.mount >
13ms initrd-udevadm-cleanup-db.service >
13ms systemd-modules-load.service >
11ms rpc-statd-notify.service >
10ms sys-fs-fuse-connections.mount >
8ms sys-kernel-config.mount >
8ms modprobe@configfs.service >
8ms tmp.mount >
6ms modprobe@fuse.service
