Earlier quoted context omitted.
I think Sun must've tried and failed. Boot times on late 90's era Solaris/Sparc systems were atrocious compared to Linux/x86 systems of the day.
Just to underscore this, here's a video of some guy booting an Ultra 45, the last workstation Sun ever made. It takes 30s just to go from power-on to firmware initialized and another minute and a half to start Solaris. Older equipment such as a SPARCStation 20 would take much longer. https://www.youtube.com/watch?v=BjshAKzhxTE
Linux Kernel Fastboot [pdf]
111–120 of 121 posts
Re: Linux Kernel Fastboot [pdf]
#112Earlier quoted context omitted.
Most of the bloat isn’t from the kernel. That’s the last thing you really optimize after getting rid of all the background services, startup tasks, etc.
Clear kernel performed better in every single test run by phoronix, except one (because it has retpoline and others did not). https://www.phoronix.com/scan.php?page=article&item=arch-ant...
Re: Linux Kernel Fastboot [pdf]
#113Earlier quoted context omitted.
SATA controller firmware has a hard-coded “drive predelay” that waits before enumerating attached devices, a relic from the days long before SSDs. Even when an option to set a custom amount is available in the BIOS, it is in addition to and not instead of, as there’s no bus master to tell it all attached disks have init and the controller may speak to them. It wouldn’t necessarily have to be done synchronously up fro…
The delay in question is in initializing the Linux driver, not in the system firmware scanning for bootable devices before running Linux. The Linux driver may be taking a while for similar reasons as the firmware delay you describe. The hard drive predelay is also not as obsolete as you may think; I've encountered high-capacity SATA SSDs that take a surprisingly long time to come up after being hotplugged, to the poi…
I’m willing to bet if the stack enforced tighter tolerances for modern non-rotating disks, manufacturers wouldn’t be able to slip such shoddy firmwares into production.
Re: Linux Kernel Fastboot [pdf]
#114Earlier quoted context omitted.
The only valid approach is to remove the battery and plug it into a kill-a-watt or similar.
Performance and power saving features are vastly different between battery and AC so I don't feel that is relevant at all. If we are talking about battery-life at least.
In fact, what mobile device manufacturers have learned is that the best way to save power is to ramp up power to complete a non-IO task in as little time as possible then go back to a lower TDP as that is where peak efficiency (rather than minimal consumption) lies.
Re: Linux Kernel Fastboot [pdf]
#115Earlier quoted context omitted.
What about it? It doesn't seem to be enormously useful, given I can do so much better on my own. I got the laptop to have well-supported hardware, not because I was expecting a lot of help from Dell.
Is that all there is to it, just well supported hardware? Dell didn't configure Redhat in any way, to make better use of the hardware? I'm thinking trackpad, sleep and hibernation, graphics etc.?
And no, it seems they didn't. They haven't forced deep sleep, for example.
Re: Linux Kernel Fastboot [pdf]
#116Earlier quoted context omitted.
The XPS 13 9380 is available with Linux pre-installed, why would you want to mess with that? Or was it a fun/hobby thing?
I feel that going from 8W to 3W, while gaining a more usable system that also sits on ZFS instead of ext4, is more than enough reason. ext4 doesn't detect corruption . How am I supposed to trust it?
My Dell has an Sk Hynix NVMe drive that apparently doesn't have safe write on power failure. I know because it somehow woke up in my bag and ran the laptop battery down to 0.
BTRFS was not happy with the state of anything on the drive. I was able to do a rescue copy and verify it with my backups, so after a full restore everything turned out OK.
Re: Linux Kernel Fastboot [pdf]
#117Earlier quoted context omitted.
Clear kernel performed better in every single test run by phoronix, except one (because it has retpoline and others did not). https://www.phoronix.com/scan.php?page=article&item=arch-ant...
I think you misunderstood. I was saying in a typical stack, time from POST to desktop is significantly overshadowed by userland bloat, not that Clear kernel is not worth the optimization.
Re: Linux Kernel Fastboot [pdf]
#118Earlier quoted context omitted.
Is that all there is to it, just well supported hardware? Dell didn't configure Redhat in any way, to make better use of the hardware? I'm thinking trackpad, sleep and hibernation, graphics etc.?
Ubuntu, not Redhat. And no, it seems they didn't. They haven't forced deep sleep, for example.
Re: Linux Kernel Fastboot [pdf]
#119Earlier quoted context omitted.
Clear Linux is blazing fast (compiled with Intel compilers), and supposedly has a strong security model -- but it also has an extremely limited package selection. To the point that it's just not usable for me. Also, its package manager forces you to install "bundles" of somewhat related packages rather than just the specific packages you want and their deps. Maybe I'm missing something, but I find this very odd.
> compiled with Intel compilers This is a common misconception. It's not built with ICC, it's built with GCC (and some parts maybe with Clang). When did you try Clear? They have about 6200 packages now, but I'm not sure if that's still "limited" in relative terms.
Last time I tried it was a couple of months ago. I don't recall what it was missing, but it was some core part of my normal python development environment.
Re: Linux Kernel Fastboot [pdf]
#120Earlier quoted context omitted.
Performance and power saving features are vastly different between battery and AC so I don't feel that is relevant at all. If we are talking about battery-life at least.
Yes, and that would be accounting for the wrong thing. Battery life can be stretched out with user hostile things like lowering the brightness to two-digit nits and disabling all background tasks, none of which really help gauge the efficiency . In fact, what mobile device manufacturers have learned is that the best way to save power is to ramp up power to complete a non-IO task in as little time as possible then go…
I think most people are interested in their battery life when they are measuring their battery life.
Numbers you get while plugged in won't have any relevance to battery life or performance. That even applies to mobile devices, despite their learnings.