Hi Ian,
I use systemd-analyze blame:
~$ systemd-analyze
Startup finished in 35.673s (kernel) + 6.998s (userspace) = 42.671s
graphical.target reached after 6.974s in userspace
~$ systemd-analyze blame
4.156s NetworkManager-wait-online.service
1.657s plymouth-start.service
1.272s dev-sda2.device
715ms apparmor.service
660ms udisks2.service
651ms plymouth-read-write.service
477ms systemd-journal-flush.service
448ms motd-news.service
412ms upower.service
367ms networkd-dispatcher.service
329ms ModemManager.service
328ms keyboard-setup.service
317ms systemd-journald.service
314ms NetworkManager.service
296ms systemd-udev-trigger.service
246ms apport.service
238ms avahi-daemon.service
234ms accounts-daemon.service
216ms grub-common.service
181ms systemd-rfkill.service
181ms alsa-restore.service
177ms lm-sensors.service
164ms swapfile.swap
156ms systemd-logind.service
152ms systemd-timesyncd.service
149ms snapd.service
139ms plymouth-quit-wait.service
138ms pppd-dns.service
136ms lightdm.service
131ms systemd-resolved.service
125ms gpu-manager.service
115ms wpa_supplicant.service
105ms rsyslog.service
94ms [email protected]
93ms systemd-udevd.service
90ms systemd-modules-load.service
71ms snapd.seeded.service
51ms systemd-sysctl.service
51ms polkit.service
49ms packagekit.service
46ms systemd-remount-fs.service
42ms dev-hugepages.mount
41ms systemd-backlight@backlight:acpi_video0.service
38ms ufw.service
37ms sys-kernel-debug.mount
36ms kmod-static-nodes.service
33ms kerneloops.service
33ms dev-mqueue.mount
32ms geoclue.service
32ms systemd-tmpfiles-setup-dev.service
30ms
systemd-fsck@dev-disk-by\x2duuid-b8e8a7bf\x2dc29a\x2d4826\x2da0e3\
30ms
systemd-fsck@dev-disk-by\x2duuid-249e1866\x2dc377\x2d4009\x2d845e\
28ms sys-kernel-config.mount
27ms systemd-random-seed.service
25ms systemd-tmpfiles-setup.service
24ms sys-fs-fuse-connections.mount
23ms home.mount
20ms console-setup.service
19ms boot.mount
14ms systemd-tmpfiles-clean.service
14ms systemd-user-sessions.service
11ms ureadahead-stop.service
9ms systemd-update-utmp-runlevel.service
8ms systemd-update-utmp.service
3ms setvtrgb.service
3ms snapd.socket
~$ 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 @6.974s
└─multi-user.target @6.973s
└─kerneloops.service @6.938s +33ms
└─network-online.target @6.937s
└─NetworkManager-wait-online.service @2.779s +4.156s
└─NetworkManager.service @2.457s +314ms
└─dbus.service @2.422s
└─basic.target @2.314s
└─sockets.target @2.314s
└─snapd.socket @2.311s +3ms
└─sysinit.target @2.308s
└─apparmor.service @1.592s +715ms
└─local-fs.target @1.581s
└─home.mount @1.557s +23ms
└─systemd-fsck@dev-disk-by\x2duuid-249e1866\x2dc377\x2d40
└─dev-disk-by\x2duuid-249e1866\x2dc377\x2d4009\x2d845e\
14.05.2018 11:48, Ian Bruntlett пишет:
Hi RB,
On 14 May 2018 at 09:42, RB <[email protected]
<mailto:[email protected]>> wrote:
Ubuntu 18.04 slow boot and shutdown
Good day!
After upgrading from Ubuntu 17.10 to lub Although 18.04 LTS (Bionic
Beaver), loading and unloading became slow, instead of 10-15 seconds
more than a minute.
What can be done?
I have noticed that some shutdowns can be slower because security
updates are being applied. I would like the option to have the system
tell me that it is doing that. That is one possibility.
This command will help you analyse system boot-up perfornance:
systemd-analyze blame
HTH,
Ian
--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software
--
Lubuntu-users mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
