It does not matter unless you reboot your machine every hour.
this post was submitted on 30 Jun 2023
4 points (100.0% liked)
Linux
48008 readers
1505 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Literally don't personally care about boot time, as long as it's under 30-60s (currently at about ~5?), and since I reboot like once a month, I don't really pay much attention to it. How come you want to minimize that so much? Any particular target you want to achieve?
I really just wanted to get a gauge on what a good range is. For my machine, I just want to see how low I can get it without sacrificing needed features or maintainability. 10s would be amazing.
Stop rebooting, problem solved!
# systemd-analyze time
Startup finished in 39.050s (firmware) + 6.680s (loader) + 993ms (kernel) + 3.519s (initrd) + 22.326s (userspace) = 1min 12.570s
graphical.target reached after 21.680s in userspace.
for me, most time is used until the bootloader shows up, because I had to disable "fast boot" in bios because it made some problems on rebooting. pressing enter in grub could speed up 5 seconds more ;-) gentoo, systemd, 2x2tb nvme, 32 gb ram, 4 hdds. could be faster, but it mostly doesn't matter because I power on the system every morning but don't use it right away
edit: on my server, which is not UEFI, therefore has no "firmware" part:
# systemd-analyze time
Startup finished in 1.814s (kernel) + 47.640s (initrd) + 36.602s (userspace) = 1min 26.057s
graphical.target reached after 36.602s in userspace.
and on my laptop, which boots fast AF
# systemd-analyze time
Startup finished in 4.242s (firmware) + 14.631s (loader) + 1.737s (kernel) + 3.210s (initrd) + 5.136s (userspace) = 28.959s
graphical.target reached after 4.936s in userspace.
That seems like a lot of time in firmware! The laptop time is amazing though.
-
a few minutes. Usually I expect 2, claim 5, but when updating gitlab or something equally bloated I'll need 7-10 for the patch-and-bounce.
-
no one cares whether it takes a minute extra while you're getting coffee or when it's in the middle of the night. The #1 selling feature of systemd is thus moot and it's truly just a piece of hot garbage.
Linux 6.5 Should Spend Less Time Waiting On PCIe Devices: https://www.phoronix.com/news/Linux-6.5-PCI
My server takes about a minute but it's a dual core Atom with 1.8gb of ram >_<
About twenty seconds from 'power button' to 'desktop' on my laptop, about two minutes on my desktop, mainly because it's got about 9 disks in it in various RAID patterns, and a discrete graphics card and fancy USB audio and all that shit needs initialised. Doesn't matter much, they both sleep / hibernate and rarely need restarted
Interesting - I also have a discrete GPU and a USB interface. Do these things add much time?
We're talking seconds, but on top of 'twenty seconds' then it's a large fraction of the total. The real problem is mounting disks in RAID for me, though - takes quite a while.
Last time I rebooted the laptop it was about 30 seconds... six months ago.
Seriously guys, why the boot time that important nowadays ?
view more: next ›