Originally posted by TheLexMachine
View Post
Announcement
Collapse
No announcement yet.
How Intel's Clear Linux Team Cut The Kernel Boot Time From 3 Seconds To 300 ms
Collapse
X
-
-
Originally posted by Michael View Post
Why not just use Clear Linux itself?
Leave a comment:
-
Originally posted by hotaru View Post
while you can disable the ~3 second timeout for entering setup, those 3 seconds are insignificant compared to the 15 or more seconds the firmware takes regardless of the quick boot setting.
Leave a comment:
-
Originally posted by kokoko3k View Postboot with mem=xxxxm (but how to add the memory back?)
- Likes 2
Leave a comment:
-
Originally posted by caligula View PostI could probably shave off few seconds from kernel/userspace and disable the boot loader, but I couldn't find any way to optimize the UEFI firmware beyond 16 seconds.
Found an example from notes:
Startup finished in 35min 59.223s (firmware) + 3.864s (loader) + 1.075s (kernel) + 2.386s (userspace) = 36min 6.549s
Originally posted by hotaru View Postwhile you can disable the ~3 second timeout for entering setup, those 3 seconds are insignificant compared to the 15 or more seconds the firmware takes regardless of the quick boot setting.
I believe I had sub 1 second for kernel/userspace, and about 5 seconds for firmware. It's not an expensive motherboard, ASRock with H170 chipset for a i5-6500 Skylake, Crucial MX300 SSD. From there you've reached the DM and with that setup for autologin to the DE(KDE Plasma in my case), total time until usable desktop from cold boot was about 12 seconds I think?
I don't think there is anything special about my firmware, the motherboard did have an issue with some hardware clock resetting upon resume from suspend(affected my para-virtualized VM), I e-mailed ASRock support and they sent me a new firmware to flash that fixed that.
So uhh.. I guess my system boots in less time than your firmware takes? How old is your system? Could be that you have an outdated perspective of what more modern hardware is capable of, either that or your vendor writes poor firmware?(could be that your system has more work to initialize, I know that server grade hardware for enterprises can have ridiculously slow boot times)
I can't recall what the boot time for my firmware is like without enabling one of the FastBoot settings, I haven't bothered timing for a couple years now, maybe 20 seconds tops.
I have these results from my old notes when I did play around with it:
Startup finished in 647ms (kernel) + 461ms (userspace) = 1.109s
Startup finished in 53min 47.652s (firmware) + 3.300s (loader) + 307ms (kernel) + 839ms (initrd) + 790ms (userspace) = 53min 52.890s
Startup finished in 9.442s (firmware) + 938ms (loader) + 308ms (kernel) + 835ms (initrd) + 729ms (userspace) = 12.254s
Other variances were from messing around with different boot params, disabling services at boot that weren't necessary, trying different compression, etc.
Leave a comment:
-
Originally posted by M@GOid View Postyou loose the ability to enter again on the UEFI interface, until you erase the CMOS...
- Likes 2
Leave a comment:
-
Originally posted by starshipeleven View PostMore like "linux teams never needed to show off like this".
Kernel boot times of 3 seconds are more or less irrelevant when BIOS/UEFI part takes up to 10 seconds, or the onboard flash (embedded system) takes 5 seconds to read on boot, or the SoC init phase takes nearly 20 seconds (modern Qualcomm-Atheros SoCs for routers for example), and also the rest of the OS boot takes again 10 seconds with systemd or some minutes with SysV-like crap.
Leave a comment:
-
Originally posted by M@GOid View Post@R41N3R
@starshipeleven
Actually, most UEFI/BIOS have a option for quick boot. In fact, a Gigabyte mobo I have has a option that boots so fast, you loose the ability to enter again on the UEFI interface, until you erase the CMOS...
- Likes 1
Leave a comment:
-
It would be nice to see these types of changes applied to a common KVM/QEMU guest kernel configuration such as the virtio drivers.
There seems to periodically be edge cases were hot-migrations between hypervisors just does not work or is not an option. In those cases, the ability to shave 2 more seconds off the VM boot after a cold migration could have some benefits.
- Likes 1
Leave a comment:
Leave a comment: