4 ms·
I'm on a very lean Linux on a fast machine. It boots near instantly: I think one second between entering the encrypted disk's password and then the login screen
by TacticalCoder 3y ago
I'm on a very lean Linux on a fast machine. It boots near instantly: I think one second between entering the encrypted disk's password and then the login screen.
... $ time emacs -Q -eval '(kill-emacs)'
Takes 86 milliseconds I think. That's launching graphical Emacs on a 4K display (well nearly: 3840x1600) ("-nw" / "no window" would be even faster), running elisp code, and exiting back to the terminal.
I'm running the very small "Awesome WM" tiling WM with 12 virtual workspaces and switching between them is ultra snappy.
Now, sure, countless websites using way too much unnecessary monothreaded JavaScript and calling way too many microservices have insufferable network
and redraw latency (even though I've got a fat and low-latency fiber pipe to the home), but my computer is still incredibly snappy.
My Ryzen 7000 series CPU is so quick I actually set it to always be in "eco mode" (in the BIOS/UEFI) and don't bother to run it at its max speed.
I'd say hardware is amazing compared to what we had in the past and software, if you're careful, can be very snappy.
That thing will reach months of uptime if I want: not just the OS but the software as well. I'll reboot for critical security updates mandating a reboot (extremely rare) and when I go on vacation but that's about it.
I know, I know, I should turn it off: but the thing is so stable I don't even bother. At night I switch to a virtual workspace that puts the CPU in "powersave" mode (actually of my 12 virtual workspaces, only the one where I "dev" turns the CPU to performance mode and as soon as I switch to another workspace, I put the CPU back to powersave: hence broken JavaScript pages won't make my fans runs loud).