Comment by toomanyducks
5 years ago
Assuming 'less than a few seconds' is actually accurate, that's not quite the case - I dual boot with a NVMe and SATA SSD, and even the NVMe (running Void Linux with runit) still takes about 30 seconds to power on. Absolutely 'fast enough' and not really something I think is worth the effort to lessen, but still not less than a few seconds.
That seems very extreme. My Arch install on an M.2 SSD boots to terminal in about 3 seconds, and X starts in about a second. The BIOS delay is roughly 5 seconds or so. Granted it's a fairly minimal install, but that shouldn't cause an order of magnitude difference.
I don't think runit has an equivalent for `systemd-analyze blame`, but something is probably slowing things down by a lot.
I would not put up with anything more than 10-15 seconds on my stock (but not bloated) Arch with Systemd and a cheap SSD.
I wonder what's going on.
My firewall is an AMD 5130 (pre Zen) with 4 GB RAM and a SATA SSD, running Debian stable with sysvinit. It reboots in less than 30 seconds, which means that most of the time TCP sessions passing through it stay up.
How much RAM do you have installed? That can significantly affect your boot time.
Maybe try systemd, the boot times are legitimately quicker.