Kuna nüüd on systemd ajastu, siis võiks kontrollida üksteiste süsteemi laadimist:
~$ systemd-analyze
Startup finished in 5.801s (kernel) + 20.616s (userspace) = 26.418s
Kui asi üle minuti laeb, siis on systemd millestki ilma.
systemd ja startup
Moderaator: Moderaatorid
systemd ja startup
ricochet:yckka6zlbxv767lz
Re: systemd ja startup
Pigem on see tihti ikkagi puhtalt "rauas" kinni, kasvõi selles kas su Distro töötab ainult kettalt või teeb hoopis mällu ajutise RAM Diski ja laeb oma töökraami sinna ajutisse RAM Diski.tris kirjutas:Kuna nüüd on systemd ajastu, siis võiks kontrollida üksteiste süsteemi laadimist:
~$ systemd-analyze
Startup finished in 5.801s (kernel) + 20.616s (userspace) = 26.418s
Kui asi üle minuti laeb, siis on systemd millestki ilma.
----
Ning teise asjana - kõik on kinni ka selles kas protsessorit jooksutatakse täisvõimsusel või mitte. Seda näeb kasvõi Sysinfo vahendusel - et mis kiirusega protsessor tegelikult töötab:
Näide: Elementary OS ning kasutab prosat hetkel ikka oluliselt aeglasemalt kui on max. kiirus

Ning kolmandana - kui tahad, et kõik käiks väga siva, siis vajad ikkagi SSD-d.
Palju sõltub ka teenustest:
~$ systemd-analyze blame
6.510s NetworkManager-wait-online.service
4.763s dev-sda1.device
4.203s tuptime.service
4.058s NetworkManager.service
2.687s ModemManager.service
2.351s ufw.service
2.210s accounts-daemon.service
2.127s networking.service
1.977s lightdm.service
1.798s irqbalance.service
1.717s grub-common.service
1.482s ondemand.service
1.283s apparmor.service
1.176s linuxlogo.service
976ms systemd-logind.service
960ms keyboard-setup.service
940ms gpu-manager.service
930ms rsyslog.service
896ms systemd-tmpfiles-setup-dev.service
783ms systemd-udevd.service
738ms polkitd.service
720ms udisks2.service
673ms systemd-fsck@dev-disk-by\x2duuid-5ae27416\x2d9569\x2d464d\x2db3c5\x2dccd0a2bcb769.service
568ms systemd-rfkill.service
544ms pppd-dns.service
495ms console-setup.service
426ms binfmt-support.service
426ms systemd-tmpfiles-setup.service
411ms apport.service
385ms systemd-backlight@backlight:acpi_video0.service
374ms systemd-journald.service
336ms systemd-backlight@backlight:nv_backlight.service
237ms systemd-udev-trigger.service
236ms dev-mqueue.mount
226ms wpa_supplicant.service
206ms systemd-modules-load.service
196ms resolvconf.service
193ms home.mount
174ms ntp.service
162ms alsa-restore.service
153ms systemd-sysctl.service
135ms kmod-static-nodes.service
126ms sys-kernel-debug.mount
124ms dev-hugepages.mount
106ms user@1000.service
100ms dev-disk-by\x2duuid-561a8672\x2d87ce\x2d40c4\x2d8467\x2d0366545401ff.swap
~$ systemd-analyze blame
6.510s NetworkManager-wait-online.service
4.763s dev-sda1.device
4.203s tuptime.service
4.058s NetworkManager.service
2.687s ModemManager.service
2.351s ufw.service
2.210s accounts-daemon.service
2.127s networking.service
1.977s lightdm.service
1.798s irqbalance.service
1.717s grub-common.service
1.482s ondemand.service
1.283s apparmor.service
1.176s linuxlogo.service
976ms systemd-logind.service
960ms keyboard-setup.service
940ms gpu-manager.service
930ms rsyslog.service
896ms systemd-tmpfiles-setup-dev.service
783ms systemd-udevd.service
738ms polkitd.service
720ms udisks2.service
673ms systemd-fsck@dev-disk-by\x2duuid-5ae27416\x2d9569\x2d464d\x2db3c5\x2dccd0a2bcb769.service
568ms systemd-rfkill.service
544ms pppd-dns.service
495ms console-setup.service
426ms binfmt-support.service
426ms systemd-tmpfiles-setup.service
411ms apport.service
385ms systemd-backlight@backlight:acpi_video0.service
374ms systemd-journald.service
336ms systemd-backlight@backlight:nv_backlight.service
237ms systemd-udev-trigger.service
236ms dev-mqueue.mount
226ms wpa_supplicant.service
206ms systemd-modules-load.service
196ms resolvconf.service
193ms home.mount
174ms ntp.service
162ms alsa-restore.service
153ms systemd-sysctl.service
135ms kmod-static-nodes.service
126ms sys-kernel-debug.mount
124ms dev-hugepages.mount
106ms user@1000.service
100ms dev-disk-by\x2duuid-561a8672\x2d87ce\x2d40c4\x2d8467\x2d0366545401ff.swap
ricochet:yckka6zlbxv767lz



