I just wondered if the following outputs from
systemd-analyze blame
and systemd-analyze critical-chain
look ok. Is there anything I can do to improve boot-up time?Code: Select all
systemd-analyze blame
6.012s NetworkManager-wait-online.service
2.678s vboxdrv.service
1.752s dev-sda9.device
1.447s networking.service
1.230s accounts-daemon.service
982ms ModemManager.service
905ms systemd-logind.service
824ms ufw.service
785ms NetworkManager.service
763ms avahi-daemon.service
601ms loadcpufreq.service
583ms cpufreqd.service
557ms irqbalance.service
556ms apparmor.service
550ms lvm2-monitor.service
547ms ondemand.service
474ms lightdm.service
469ms apport.service
457ms grub-common.service
445ms console-setup.service
408ms console-kit-log-system-start.service
392ms speech-dispatcher.service
374ms cpufrequtils.service
348ms iio-sensor-proxy.service
334ms keyboard-setup.service
296ms alsa-restore.service
264ms polkitd.service
238ms systemd-udev-trigger.service
223ms upower.service
223ms binfmt-support.service
217ms lm-sensors.service
192ms gpu-manager.service
191ms rsyslog.service
182ms systemd-rfkill.service
163ms pppd-dns.service
156ms systemd-journald.service
144ms thermald.service
141ms systemd-user-sessions.service
136ms systemd-update-utmp.service
135ms user@1000.service
126ms udisks2.service
113ms glances.service
107ms ntp.service
97ms systemd-modules-load.service
91ms systemd-fsck@dev-disk-by\x2duuid-E840\x2d5E8E.service
79ms proc-sys-fs-binfmt_misc.mount
65ms systemd-udevd.service
62ms systemd-journal-flush.service
52ms hddtemp.service
50ms dev-hugepages.mount
47ms sys-kernel-debug.mount
45ms dns-clean.service
44ms kmod-static-nodes.service
42ms systemd-tmpfiles-clean.service
41ms vboxautostart-service.service
40ms systemd-tmpfiles-setup-dev.service
39ms resolvconf.service
38ms vboxballoonctrl-service.service
37ms plymouth-read-write.service
36ms dev-mqueue.mount
34ms vboxweb-service.service
31ms systemd-tmpfiles-setup.service
29ms rc-local.service
26ms openvpn.service
25ms sys-kernel-config.mount
25ms systemd-sysctl.service
24ms setvtrgb.service
Code: Select all
systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @9.402s
└─multi-user.target @9.400s
└─glances.service @9.262s +113ms
└─network-online.target @9.253s
└─NetworkManager-wait-online.service @3.239s +6.012s
└─NetworkManager.service @2.434s +785ms
└─dbus.service @2.344s
└─basic.target @2.287s
└─sockets.target @2.281s
└─uuidd.socket @2.281s
└─sysinit.target @2.270s
└─apparmor.service @1.712s +556ms
└─local-fs.target @1.683s
└─run-cgmanager-fs.mount @2.657s
└─local-fs-pre.target @801ms
└─lvm2-monitor.service @250ms +550ms
└─lvm2-lvmetad.service @292ms
└─lvm2-lvmetad.socket @249ms
└─-.slice @177ms