Post your avergage boot-time

>>56841180
Startup finished in 3.459s (firmware) + 4.201s (loader) + 2.981s (kernel) + 6.288s (userspace) = 16.931s

Startup finished in 4.847s (kernel) + 3.980s (userspace) = 8.828s

Startup finished in 4.655s (kernel) + 818ms (userspace) = 5.473s

Arch/KDE5

Startup finished in 9.087s (kernel) + 5.193s (userspace) = 14.280s

>>56841180
what is the best way to fasten my boot time? i have i5-5200u, SSD and 16GB ram still my boot time is more than 13 secs

Startup finished in 15.675s (kernel) + 1min 30.225s (userspace) = 1min 45.900s

Pi 1, Raspbian Jesse:
Startup finished in 3.448s (kernel) + 27.011s (userspace) = 30.460s

Pi 2, Retropie:
Startup finished in 11.207s (kernel) + 16.181s (userspace) = 27.389s

Pi 3, LibreELEC 7.90.006:
Startup finished in 3.877s (kernel) + 2.563s (userspace) = 6.441s

>>56841180
is that image true? i'm sleeping like 10h every night.

>>56841180
Wondering why my boottime is still 16 seconds despite 8GB ram and an SSD

Startup finished in 7.715s (kernel) + 4.263s (userspace) = 11.978s

I think it's not too bad for a netbook.

>>56841647
It's predicated on the assumption that the only sleep you need is REM sleep, which i think is presumptive.

>>56841180

I have to wait like 15 seconds for the PSU to generate reliable power so it can even start booting. Then like 30 seconds more to boot.

>>56841652
mine too

>>56841687
wtf do you have a gas powered psu

Startup finished in 8.534s (kernel) + 34.575s (userspace) = 43.110s

File: 1472358141202.jpg (984KB, 2560x1920px) Image search: [Google]

984KB, 2560x1920px

>>56841647
it's a mega meme

>>56841180
Startup finished in 4.576s (kernel) + 7.815s (initrd) + 12.058s (userspace) = 24.449s

Not mentioned are the 30-60 seconds or so I need to get through BIOS

>>56841180
Startup finished in 13.093s (firmware) + 1.962s (loader) + 2.139s (kernel) + 1.802s (userspace) = 18.997s

No idea why it's taking so long. My Thinkpad is way faster.

>>56841180
Startup finished in 4.129s (kernel) + 14.181s (userspace) = 18.310s

HDD-Arch-i3wm

>>56841579
1. Find the bottlenecks
2. Optimize the bottlenecks

Start with #1.

>>56841895
How do you get a measure of the firmware/loader initialization time like that?

Does it require using UEFI?

>>56842133
Probably because I'm using systemd-boot. Not sure though.

>>56842117
Nice of you to mention to start with #1. I was about to start with #2

>>56841180
Startup finished in 5.524s (kernel) + 21.988s (userspace) = 27.512s

>>56842361
'systemd-analyze blame' is your friend

Tip: Get rid of grub and setup uefi boot. (maybe keep grub somewhere else for recovery)

Startup finished in 4.240s (firmware) + 2.670s (loader) + 4.067s (kernel) + 9.708s (userspace) = 20.687s

>>56842424
probably need this. Also my SSD is gonna die soon. Windows cant even run properly with it. When there is some read and write on the SSD windows freezes and the SSD spikes to 100k ms response time.

File: 010212dukakis.jpg (128KB, 1183x800px) Image search: [Google]

128KB, 1183x800px

>>56841180
I don't think systemd-analyze actually gives you the time it takes to get to the desktop. I use kde and I get the distinct impression systemd considers the job done after sddm says its running.

File: maki is cute 469.png (230KB, 685x580px) Image search: [Google]

230KB, 685x580px

Startup finished in 17.695s (firmware) + 102ms (loader) + 23.027s (kernel) + 4.746s (userspace) = 45.572s

Startup finished in 79.953s (firmware) + 16.851s (loader) + 32.981s (kernel) + 6.368s (userspace) = 16.931s

>>56841180

Startup finished in 2.458s (kernel) + 780ms (userspace) = 3.238

debian testing

>>56842338
That sounds like it must be the case. Is systemd-boot some UEFI thing like rEFInd?

My main complaint about grub is that it makes sharing /boot with a VM a pain. rEFInd might solve that.

>>56842506
Yeah systemd is just measuring the time it needs to reach the graphical.target. Any initialization after that point (like loading the KDE desktop) is the responsibility of the graphical software you're using.

My latest boot was 40s of which ~35s is userspace (booting straight into gnome 3, bypassing gdm). It was over a minute until I deleted the systemd journal and disabled some useless services. Now I think the network manager is the main offendor but 40s is good enough for now.

Seems fedora is one of the slower distros for booting into.

Startup finished in 1.203s (firmware) + 5.529s (loader) + 1.923s (kernel) + 8.124s (userspace) = 16.781s

File: 74436680808.jpg (16KB, 559x556px) Image search: [Google]

16KB, 559x556px

>>56841847
>30-60 seconds to get through BIOS

Do I run that on cmd.exe or Power Shell™?

Startup finished in 3.282s (kernel) + 4.932s (userspace) = 8.215s

Startup finished in 8.656s (kernel) + 10min 42.063s (userspace) = 10min 50.719s

>>56843033
It is what it is. Slow firmware initialization on the part of my motherboard

File: 2016-09-25-162657_642x362_scrot.png (10KB, 642x362px) Image search: [Google]

10KB, 642x362px

>>56841180

>>56841180
4.553s

>>56842361
That's what most novice programmers try to do

Startup finished in 9.840s (kernel) + 14.770s (userspace) = 24.610s
Definitely have to buy an SSD

Startup finished in 3.006s (kernel) + 12.111s (userspace) = 15.118s

Startup finished in 3.187s (kernel) + 18.012s (userspace) = 21.199s

>>56841180
Startup finished in 1.214s (kernel) + 21.002s (initrd) + 40.390s (userspace) = 1min 2.607s

Startup finished in 2.610s (kernel) + 1.706s (userspace) = 4.317s

Startup finished in 2.153s (kernel) + 2.124s (initrd) + 55.211s (userspace) = 59.489s

>>56841180
Debian Cinnamon here:

Startup finished in 3.305s (kernel) + 18.948s (userspace) = 22.253s

>>56841647
Don't try that shit, it will fuck you up.

>>56841180
Startup finished in 2.674s (firmware) + 5.733s (loader) + 22.594s (kernel) + 1min 9.178s (userspace) = 1min 40.180s

It's actually faster, but the man-db service does that sometimes

btw, all fucking captchas have "Calle" for some reason

>>56845339
what

>>56841180
I just slept for only 20 minutes today and I feel refreshed.
Can't wait for bad drop tomorrow.

>>56841647
Yes, but no real clinical studies have been done on the long term effects of it. It could be very detrimental to your health, or not. No one knows. Just because your body has been tricked into thinking it's well rested, doesn't mean that it actually is.

Also, it comes with a price. Right now when you are tired, you can keep going if you need to. With power napping, when nap time comes, you are going to pretty much just nod out, whether you want to or not.

im on a pentium 4 shitbox and it totals like 16.5 seconds with grub

>>56841180
Startup finished in 1min 8.595s (kernel) + 12.344s (userspace) = 1min 20.940s
takes so long because of LUKS, won't boot without me entering the passphrase

File: 1471635529835.jpg (82KB, 630x776px) Image search: [Google]

82KB, 630x776px

>>56841180
>>for the majority of /g/
>he thinks that majority of /g/ uses Lincuc'ks

>>56841180
Is there a part two to this article? It seems like a fun read, although it's probably mostly crap.

>>56847552
it does

>>56844431
>It is what it is. Slow firmware initialization on the part of my motherboard
what mobo is that? I need to know so I never buy that chink piece of shit.

>>56847575
you're fucking delusional. go look at desktop threads. go look at SQT. it's mostly windows.

File: Sayaka realizes that autism is real.png (164KB, 256x512px) Image search: [Google]

164KB, 256x512px

>>56847575
>being this retarded

>>56847585
ASRock EP2C602

Slow POST is pretty common for server motherboards with hundreds of PCI devices though, good luck getting around it. I have servers at work that post even more slowly (mostly because they insist on waiting several seconds for a DHCP/PXE reply on every single NIC). Also, it spends at least some of that time doing self-checks and logging their results to the IPMI SEL.

Don't worry though, your consumer trash mainboards are unaffected :^)

>ITT Sloths, turtles and slugs

Startup finished in 941ms (kernel) + 2.820s (userspace) = 3.762s