zlacker

[parent] [thread] 5 comments
1. tooman+(OP)[view] [source] 2021-05-22 20:06:12
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.
replies(5): >>dsr_+ra >>jorams+Be >>gnull+Nm >>eptcyk+1S >>Sephr+IU
2. dsr_+ra[view] [source] 2021-05-22 21:39:19
>>tooman+(OP)
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.

3. jorams+Be[view] [source] 2021-05-22 22:16:15
>>tooman+(OP)
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.

4. gnull+Nm[view] [source] 2021-05-22 23:49:01
>>tooman+(OP)
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.
5. eptcyk+1S[view] [source] 2021-05-23 07:58:34
>>tooman+(OP)
Maybe try systemd, the boot times are legitimately quicker.
6. Sephr+IU[view] [source] 2021-05-23 08:39:01
>>tooman+(OP)
How much RAM do you have installed? That can significantly affect your boot time.
[go to top]