Hacker News Reader

Comment by fmoralesc | Hacker News Reader

That's windows. In Linux, I get this from cold boot (on an Thinkpad T495):

    > systemd-analyze 
    Startup finished in 8.878s (firmware) + 1.666s (loader) + 1.592s (kernel) + 3.265s (userspace) = 15.403s 
    graphical.target reached after 3.176s in userspace

It's crazy that the slowest part of the whole process is the firmware stuff.

View on HN

Is that wall clock time? I get 13s but actual wall clock time is more like 26 from power on to desktop. Around 30 seconds to opening a browser.

I haven't check wall clock; I would have to enable auto-login to eliminate pauses from user interaction.

> I would have to enable auto-login to eliminate pauses from user interaction.

Why? By the time you're logging in, booting is already finished.

To check at what point the system is responsive enough to launch a browser. So, not just calculating the boot times (we have that already), but from power on to launching a browser.

While that's not an entirely unreasonable idea, I note that launching a browser has its own startup time. Power on to opening a document in evince is faster than power on to launching a browser, and that's support for the original thesis in a way, but it also feels like a little much to count it against "boot time".

Reply on news.ycombinator.com