Raspberry Pi OS • Re: Booting time reduction

Here are a few things to consider:

• Look at 'sudo systemd-analyze blame' to see what services are taking the most time. Convince yourself that all of them are needed.
• Look at services that are starting that you don't need, such as triggerhappy (although most of these are probably not large contributors to boot time)
• Use RasPiOS Lite rather than a Desktop version if possible.

As KeithMck mentioned, use the fastest possible disk you can afford. I typically use USB SSD drives, but I've found that for many applications a fast MicroSD, such as a Sandisk Extreme Pro, are sufficiently fast.

If you need blindingly fast drives, look at NVME, but I personally don't recommend them for boot disks unless absolutely required.

sudo systemd-analyze blame
6.737s NetworkManager-wait-online.service
1.370s raspi-config.service
1.220s e2scrub_reap.service
1.061s wayvnc.service
1.046s dev-mmcblk0p2.device
861ms systemd-journal-flush.service
733ms udisks2.service
708ms bthelper@hci0.service
665ms ModemManager.service
583ms lightdm.service
525ms NetworkManager.service
490ms rpi-eeprom-update.service
447ms accounts-daemon.service
439ms systemd-udevd.service
370ms polkit.service
318ms cups.service
317ms user@1000.service
313ms avahi-daemon.service
309ms networking.service
293ms wpa_supplicant.service
275ms dbus.service
272ms systemd-logind.service
259ms systemd-fsck@dev-disk-by\x2dpartuuid-ec74298f\x2d01.service
243ms dphys-swapfile.service
238ms teamviewerd.service
231ms rp1-test.service
211ms glamor-test.service
186ms sshswitch.service
167ms keyboard-setup.service
148ms systemd-tmpfiles-setup.service
145ms systemd-udev-trigger.service
140ms systemd-sysusers.service
115ms systemd-tmpfiles-setup-dev.service
114ms systemd-random-seed.service
108ms systemd-journald.service
107ms bluetooth.service
106ms systemd-binfmt.service
79ms colord.service
76ms triggerhappy.service
71ms plymouth-start.service
71ms fake-hwclock.service
67ms systemd-timesyncd.service
65ms systemd-remount-fs.service
58ms systemd-sysctl.service
56ms alsa-restore.service
49ms systemd-tmpfiles-clean.service
41ms rpc-statd-notify.service
39ms systemd-rfkill.service
38ms systemd-modules-load.service
37ms boot-firmware.mount
37ms dev-mqueue.mount
37ms sys-kernel-debug.mount
36ms sys-kernel-tracing.mount
31ms proc-sys-fs-binfmt_misc.mount
30ms ifupdown-pre.service
30ms modprobe@fuse.service
30ms kmod-static-nodes.service
29ms systemd-update-utmp.service
29ms modprobe@configfs.service
28ms systemd-user-sessions.service
28ms console-setup.service
26ms plymouth-read-write.service
26ms modprobe@drm.service
15ms user-runtime-dir@1000.service
13ms rtkit-daemon.service
10ms rc-local.service
9ms systemd-update-utmp-runlevel.service
8ms modprobe@efi_pstore.service
7ms modprobe@dm_mod.service
7ms modprobe@loop.service
7ms sys-kernel-config.mount
6ms run-rpc_pipefs.mount
4ms sys-fs-fuse-connections.mount
1ms plymouth-quit-wait.service


These are services.
I am running 2 files. main.py in which almost all GPIO are used. Other is streamlit app. I am connected to wifi. Where I can get information of files, that are useful & not useful?

Statistics: Posted by spatil — Tue Jul 30, 2024 1:45 pm

---