type `systemd-analyze` into your konsole and paste the output here and share your system config.
mine is i5 3rd gen + 8gb ram + 120gb ssd
if you're not using linux and kde plasma btfo
Systemd-analyze
Jack James
Ryder Scott
You can also do systemd-analyze > output.svg or something
Adrian Reed
>Startup finished in 17.655s (firmware) + 3.271s (loader) + 1.121s (kernel) + 13.138s (initrd) + 11.865s (userspace) = 47.052s
>graphical.target reached after 6.389s in userspace
at least 10 seconds of that is unlocking partitions and iirc I have fastboot disabled
Levi Ortiz
My old Phenom II shitposting machine with HDD
systemd-analyze
Startup finished in 2.488s (kernel) + 11.444s (userspace) = 13.932s
graphical.target reached after 11.444s in userspace
Kayden Flores
My ancient i5-2500k / 8GB rig with a Crucial SSD and Fedora 28
Startup finished in 996ms (kernel) + 893ms (initrd) + 22.732s (userspace) = 24.622s
graphical.target reached after 4.221s in userspace
Oliver Sanders
~ systemd-analyze
Startup finished in 5.021s (firmware) + 161ms (loader) + 3.430s (kernel) + 10.147s (userspace) = 18.761s
graphical.target reached after 10.133s in userspace
VMWare virtual machine on i5 8600K with 4 cores allocated.
Elijah Long
$ systemd-analyze
-bash: systemd-analyze: command not found
Mason Gomez
bash-4.4$ systemd-analyze
systemd-analyze: command not found
Oliver Smith
>he uses systemd
Julian Adams
Startup finished in 20.780s (firmware) + 3.703s (loader) + 4.369s (kernel) + 16.007s (userspace) = 44.860s
Parker Perez
rc: cannot find `systemd-analyze'
Ayden Carter
>31s
This is what I got on my chinkpad
Ayden Evans
>bash: systemd-analyze: command not found
Brody Ward
LOL
Hunter Green
How the fuck does it take 30 sec too boot with an SSD?
Leo Gonzalez
kek
Startup finished in 14.792s (firmware) + 839ms (loader) + 2.254s (kernel) + 1.400s (userspace) = 19.287s
graphical.target reached after 1.400s in userspace[/quote]
Austin Torres
[CODE]
user@gentoo:systemd-analyze
bash: systemd-analyze: command not found
user@gentoo:
[/CODE]
Angel Wilson
I have an SSD and get 10.821s (kernel) + 15.512s (userspace) = 26.333s. This is actually a severe undercount because the machine takes at least another 30 seconds to get through the BIOS and spin up all the hard drives before it even starts with the kernel. If I restarted this machine more than once a month that'd probably bother me.
Matthew Hughes
could you show us a blame or a critical-chain?
just wondering if you have some long ass routines or if you just load a shitload of services
Cooper Barnes
systemd-analyze
Startup finished in 3.421s (kernel) + 1.238s (userspace) = 4.659s
graphical.target reached after 1.237s in userspace
Hardware is nothing special, FX8350 + 120GB Intel SSD
Sebastian Martin
7.675s NetworkManager-wait-online.service
4.532s zfs-import-cache.service
1.838s systemd-udev-settle.service
648ms zfs-mount.service
582ms fail2ban.service
495ms apt-daily.service
476ms apt-daily-upgrade.service
322ms libvirtd.service
291ms dev-sda1.device
261ms upower.service
181ms systemd-modules-load.service
165ms ModemManager.service
151ms lvm2-monitor.service
147ms systemd-timesyncd.service
120ms nmbd.service
119ms smbd.service
111ms swapfile.swap
105ms systemd-journald.service
stuff under 100ms snipped. I don't know why NM has its panties in a bunch, but if I had to guess its probably setting up the tangle of virtual interfaces I have from running VMs, which I think are present even if the VMs to start at boot.
Brayden Robinson
even if the VMs *don't start at boot
Josiah Collins
yeah (virtual) hardware interfaces are the primary cause of slow boot I would say
thank linux for its uptimes
Oliver Morales
i5 7th gen + 8GB ram +256GB ssd
arch + i3