• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle












  • # 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.
    
    

  • I use both on gentoo for some obscure or proprietary stuff that is not packaged in portage, like filebot, authy desktop, discord, steam and foobar2000 (including wine in 1 bundle to avoid dependencies and switching all portage packages to 32bit abi). It works well and opens me up to loads of stuff. It’s freedom in some way.

    Snap or flatpak makes no difference to me, they’re just different backends for kde discover