I don’t think that’s going to help them, AFAIK Baloo has no effect on boot speed.
Yes on a new install the indexing may cause the system to be slow but that’s temporary. I avoid that problem by temporarily disabling indexing until the computer will not be used.
This is not a powerful CPU at all. Also, if I’m not mistaken, it’s relatively old(ish)
That is a mechanical hard drive, and also not one of the fastest.
And not a lot of RAM.
For comparison, my specs:
And my PC takes about 30 seconds to boot up. And I never hibernate, don’t like it, don’t use it. Never have. So it’s from scratch, every time.
So, I might get hate for this, and a moderator or whatever/whoever might kick me on the ass for this, but that’s fine. I highly doubt your laptop starts up in 10-15 seconds. But I am prepared to be wrong sometimes. However, from experience, what I see here, and gut feeling, I don’t think so.
At least according to me.
You need an upgrade to get the desired speeds.
Mirdarthos out. Have a good night all!
That’s pretty slow.
My i5 3570K:
Startup finished in 6.982s (firmware) + 1.258s (loader) + 1.600s (kernel) + 2.694s (userspace) = 12.535s
Based on your outputs:
This looks like you booted earlier in BIOS mode? Flag should be “boot”, not “BIOS boot” How does this happen?
This made clear you are currently booting in UEFI mode.
Anyway, achieving major improvements in boot time requires to switch to a SSD.
Your disk is definitely the main reason. Here’s my systemd-analyze blame result:
18.435s NetworkManager-wait-online.service
6.467s pkgfile-update.service
3.635s systemd-udev-settle.service
877ms man-db.service
818ms systemd-timesyncd.service
802ms systemd-binfmt.service
652ms ufw.service
613ms systemd-modules-load.service
229ms zfs-mount.service
157ms ldconfig.service
150ms udisks2.service
115ms systemd-tmpfiles-clean.service
113ms lvm2-monitor.service
97ms systemd-journal-flush.service
73ms user@1000.service
54ms sanoid.service
53ms sanoid-prune.service
47ms smb.service
47ms nmb.service
37ms systemd-udevd.service
36ms systemd-udev-trigger.service
33ms NetworkManager.service
32ms systemd-journald.service
31ms upower.service
31ms teamviewerd.service
29ms polkit.service
21ms nvidia-fake-powerd.service
20ms boot.mount
20ms systemd-logind.service
20ms logrotate.service
18ms systemd-machined.service
18ms systemd-tmpfiles-setup.service
15ms pamac-daemon.service
12ms lm_sensors.service
11ms systemd-tmpfiles-setup-dev.service
9ms wpa_supplicant.service
8ms modprobe@fuse.service
7ms systemd-sysusers.service
7ms zfs-import-cache.service
7ms alsa-restore.service
21ms nvidia-fake-powerd.service
20ms boot.mount
20ms systemd-logind.service
20ms logrotate.service
18ms systemd-machined.service
18ms systemd-tmpfiles-setup.service
15ms pamac-daemon.service
12ms lm_sensors.service
11ms systemd-tmpfiles-setup-dev.service
9ms wpa_supplicant.service
8ms modprobe@fuse.service
7ms systemd-sysusers.service
7ms zfs-import-cache.service
7ms alsa-restore.service
6ms dev-disk-by\x2duuid-388de0df\x2d1d0b\x2d4f78\x2db6a7\x2d2888859d3fa1.swap
6ms systemd-rfkill.service
5ms systemd-journal-catalog-update.service
5ms linux-module-cleanup.service
5ms systemd-random-seed.service
5ms dev-hugepages.mount
5ms dev-mqueue.mount
5ms dev-disk-by\x2duuid-5af3f596\x2d1068\x2d457f\x2d9d64\x2d4db5aa649caa.swap
5ms sys-kernel-debug.mount
4ms sys-kernel-tracing.mount
4ms kmod-static-nodes.service
4ms user-runtime-dir@1000.service
4ms modprobe@configfs.service
3ms modprobe@drm.service
3ms systemd-update-utmp.service
2ms systemd-user-sessions.service
2ms systemd-update-done.service
2ms systemd-sysctl.service
1ms proc-sys-fs-binfmt_misc.mount
1ms rtkit-daemon.service
1ms tmp.mount
1ms clamav-daemon.socket
1ms systemd-remount-fs.service
1ms sys-kernel-config.mount
744us sys-fs-fuse-connections.mount
429us mdmonitor.service
My udisk2.service load time is almost 20 times faster than yours. Plus, your filesystem check fsck service took another 11 seconds.
PS: My OS is installed on NVME.
Here’s mine
[omano@omano-nvme ~]$ systemd-analyze blame
3.180s linux-modules-cleanup.service
1.429s systemd-random-seed.service
787ms systemd-modules-load.service
782ms media-SSD_500Go.mount
436ms dev-nvme0n1p2.device
312ms systemd-swap.service
224ms tlp.service
215ms apparmor.service
158ms systemd-sysusers.service
149ms systemd-journal-flush.service
128ms user@1000.service
121ms ldconfig.service
106ms polkit.service
85ms udisks2.service
65ms ModemManager.service
65ms boot-efi.mount
64ms NetworkManager.service
64ms avahi-daemon.service
57ms systemd-udev-trigger.service
56ms systemd-logind.service
51ms systemd-tmpfiles-clean.service
47ms systemd-udevd.service
42ms cups.service
34ms systemd-tmpfiles-setup.service
32ms upower.service
30ms systemd-journald.service
30ms systemd-tmpfiles-setup-dev.service
26ms systemd-timesyncd.service
[omano@omano-nvme ~]$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @2.829s
`-multi-user.target @2.829s
`-systemd-swap.service @2.516s +312ms
`-basic.target @2.505s
`-sockets.target @2.505s
`-dbus.socket @2.505s
`-sysinit.target @2.501s
`-systemd-update-done.service @2.489s +12ms
`-ldconfig.service @2.366s +121ms
`-local-fs.target @2.366s
`-run-user-1000.mount @4.372s
`-local-fs-pre.target @359ms
`-systemd-tmpfiles-setup-dev.service @329ms +30ms
`-systemd-sysusers.service @169ms +158ms
`-systemd-remount-fs.service @163ms +4ms
`-systemd-fsck-root.service @143ms +19ms
`-systemd-journald.socket @138ms
`-system.slice @129ms
`--.slice @129ms
NVME SDD here too.
Apologies. My mistake. My time-keeping is obviously faulty. Here’s mine:
$ systemd-analyze
Startup finished in 22.233s (firmware) + 5.332s (loader) + 4.894s (kernel) + 5.321s (userspace) = 37.782s
graphical.target reached after 5.321s in userspace
W$ have a trick with the boot, that is basically a file created like the hibernation file, so when you boot, 10-25s are fake, so is not comparable.
I had the same “problem”, but disabling the boot with trick of W$, I can see the same times W10 / Manjaro mate.
W$ call “fast startup”.
Mine, HDD 5400 RPM:
systemd-analyze blame
14.863s systemd-tmpfiles-clean.service
9.964s dev-sda5.device
6.086s udisks2.service
5.833s accounts-daemon.service
4.810s ldconfig.service
4.089s polkit.service
3.924s avahi-daemon.service
3.915s NetworkManager.service
3.850s systemd-homed.service
3.790s apparmor.service
3.733s auditd.service
3.355s systemd-logind.service
3.354s systemd-machined.service
2.640s systemd-journal-flush.service
2.521s systemd-sysusers.service
2.426s laptop-mode.service
1.823s systemd-modules-load.service
1.562s systemd-rfkill.service
1.514s lm_sensors.service
1.394s systemd-resolved.service
1.393s systemd-fsck@dev-disk-by\x2duuid-C043\x2d986B.service
1.091s bluetooth.service
1.056s systemd-tmpfiles-setup-dev.service
1.055s systemd-zram-setup@zram1.service
1.053s systemd-zram-setup@zram0.service
1.049s systemd-zram-setup@zram3.service
1.043s systemd-zram-setup@zram2.service
933ms systemd-journal-catalog-update.service
832ms systemd-udevd.service
665ms add-autologin-group.service
629ms user@1000.service
586ms alsa-restore.service
569ms lightdm.service
497ms systemd-fsck@dev-disk-by\x2duuid-422cc68e\x2dac78\x2d4fd8\x2db624\x2d5236e539bafb.service
487ms systemd-tmpfiles-setup.service
478ms modprobe@fuse.service
474ms systemd-journald.service
472ms systemd-timesyncd.service
446ms systemd-sysctl.service
405ms wpa_supplicant.service
379ms systemd-udev-trigger.service
353ms upower.service
353ms systemd-random-seed.service
288ms systemd-userdbd.service
270ms dev-zram2.swap
262ms dev-zram0.swap
261ms dev-zram1.swap
259ms dev-zram3.swap
247ms dev-hugepages.mount
246ms dev-mqueue.mount
246ms sys-kernel-debug.mount
246ms sys-kernel-tracing.mount
245ms kmod-static-nodes.service
245ms modprobe@configfs.service
244ms modprobe@drm.service
181ms systemd-update-utmp.service
140ms ufw.service
137ms systemd-backlight@backlight:amdgpu_bl0.service
104ms systemd-user-sessions.service
89ms boot.mount
75ms systemd-remount-fs.service
50ms sys-kernel-config.mount
47ms dev-disk-by\x2duuid-8489e5dc\x2d1fda\x2d4e96\x2db965\x2d600174e81191.swap
43ms systemd-update-done.service
41ms libvirtd.service
34ms fail2ban.service
29ms udisks2-zram-setup@zram0.service
28ms udisks2-zram-setup@zram1.service
27ms udisks2-zram-setup@zram2.service
27ms udisks2-zram-setup@zram3.service
15ms rtkit-daemon.service
9ms user-runtime-dir@1000.service
4ms boot-efi.mount
3ms sys-fs-fuse-connections.mount
2ms tmp.mount
205us systemd-homed-activate.service
This question has been asked and answered hundreds of times and possible solutions could have easily been found by using the search function. It has now evolved into a “you show me yours and I’ll show you mine” thread. Mine is fast, but I am not going to show 
Who would think we would compete on whose is shortest… 
Time for delete some snaps applications 
1.921s fwupd.service
1.505s systemd-random-seed.service
1.367s dev-loop11.device
1.342s dev-loop8.device
1.341s dev-loop12.device
1.339s dev-loop10.device
1.338s dev-loop4.device
1.336s dev-loop3.device
1.333s dev-loop9.device
1.329s dev-loop6.device
1.308s dev-loop7.device
1.306s dev-loop1.device
1.302s dev-loop5.device
1.300s dev-loop2.device
1.292s dev-loop0.device
1.081s systemd-modules-load.service
1.013s dev-nvme0n1p2.device
409ms cpupower-gui.service
381ms tlp.service
287ms snapd.service
285ms apparmor.service
276ms systemd-rfkill.service
160ms user@1000.service
136ms polkit.service
132ms systemd-udevd.service
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /var/lib/snapd/snap/bare/5
loop1 7:1 0 55.5M 1 loop /var/lib/snapd/snap/core18/2253
loop2 7:2 0 55.5M 1 loop /var/lib/snapd/snap/core18/2284
loop3 7:3 0 61.9M 1 loop /var/lib/snapd/snap/core20/1270
loop4 7:4 0 242.3M 1 loop /var/lib/snapd/snap/gnome-3-38-2004/76
loop5 7:5 0 61.9M 1 loop /var/lib/snapd/snap/core20/1328
loop6 7:6 0 164.8M 1 loop /var/lib/snapd/snap/gnome-3-28-1804/161
loop7 7:7 0 247.9M 1 loop /var/lib/snapd/snap/gnome-3-38-2004/87
loop8 7:8 0 65.2M 1 loop /var/lib/snapd/snap/gtk-common-themes/1519
loop9 7:9 0 317.6M 1 loop /var/lib/snapd/snap/retroarch/1173
loop10 7:10 0 317.7M 1 loop /var/lib/snapd/snap/retroarch/1178
loop11 7:11 0 43.3M 1 loop /var/lib/snapd/snap/snapd/14295
loop12 7:12 0 43.4M 1 loop /var/lib/snapd/snap/snapd/14549
$ pamac remove snapd
Preparing...
Checking dependencies...
Error: Failed to prepare transaction:
could not satisfy dependencies:
- removing snapd breaks dependency 'snapd' required by libpamac-snap-plugin
Now read your screen and guess why you can not remove snapd. Spoiler alert: snapd is required by libpamac-snap-plugin so guess what you need to remove now to be able to remove snapd. But this is getting more off-topic now.
Yes… but not really. The point is that people are telling OP that issue is his hard drive, people show how fast it is with SSD compared to hard drive because OP still continues to think he can overcome basic hardware facts. Point is HDD is slow, SSD is fast. Sure you can probably gain a few seconds by removing most of the “bloat”, but there is no way around having slow hardware.
I have tried the way to install hibernation my pc but still not satisfied!
Most of your boot time is in BIOS/UEFI space! 
pamac remove --cascade snapd
Yeah. Cool, huh?
I have disabled it… by sudo systemctl disable snapd.service
BTW finally I know how to reduce the boot time to enhance it
my last boot time was something 30-37s… before it was 60-70s… BTW thanks for your help guys!
pamac does not use snap by default, so why snap bring so much time delay?
systemd-analyze
Startup finished in 7.128s (firmware) + 7.237s (loader) + 894ms (kernel) + 428ms (initrd) + 1.769s (userspace) = 17.459s
graphical.target reached after 1.468s in userspace
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.