>we post our boot time

File: Picard_with_hair.jpg (157KB, 449x624px) Image search: [Google]

157KB, 449x624px

Startup finished in 14.434s (kernel) + 35.606s (userspace) = 50.041s

atom n570 netbook running debian testing, gnome

oh,
and fuck every single one of you

About 5 seconds with SSD and Windoze 8.1

>>52847518
I haven't turned my computer off in 4 months.

Boot time means nothing.

Startup finished in 4.054s (kernel) + 1.006s (userspace) = 5.061s.

MemePad x220 running Arch from SSD

>>52847518
~3 minutes to Fedora 22
~7 minutes to Win7

haven't figured out kernel live-patching yet so I don't really have good uptime on anything. I might on some servers in my basement but that never feels fair.

10 seconds with Windows 7 on SSD (not M.2).

>>52847518
32 minutes windows 10

>takes more than 1min to be accessible
>1TB WD green is almost full

>>52847681
Is that actually full boot up time? I know with 10 the only reason people are getting these crazy bootimes is because the OS is basically half sleeping/half hibernating instead of shutting off.

>>52847518
About 45 secs at most desu

>>52847518
30s, 7, SSD. Cheapo SSD though, so I don't mind.

>>52847804
>wd green
stupid cucked fool

>>52847739
ah, excuse me, I thought this was an uptime thread for some reason

Around 5 minutes.

my windows 10 PC with an i7, 16gigs of RAM, 1TB 7200rpm HDD, and GTX 680 takes no joke about 45 minutes to boot up and be in a usable state. I don't even have a bunch of programs opening at start up, just windows. If I want it to stop showing 100% disk usage in the resource manager I have to wait a full day.

All of this started happening maybe a week after installing windows "we promise it's not a botnet" 10.


My 2015 MacBook Pro on the other hand takes a grand total of 6 seconds to boot up.

>>52847949
If it even takes longer than ~10 minutes, you fucked something up somewhere.
If you want to see what is using the disk so hard, find the process that's actually using resources, and kill it with fire.

>>52847832
>Runs quiet, cool, cheap
Whats to hate about it, not everyone is Americunt who gets all the hardware at cheap ass price

21 seconds

Arch Linux on an HDD

7 seconds, Windows 10, SSD

>>52847809
Full boot time for me is about 3 seconds after the mobo powers on.
I can log into winblows and start all of my applications instantly.
SSDs are god tier

>>52847949
Shit hard drive, stupid user or ntfs partition that hasn't been defragged

>>52847949
disable superfetch.
I have had to do with with every windows build. I have my win 10 on a SSD and it boots in about 7 seconds to be usable its about 13-15 seconds.

>>52848338
anon, my computer stays at my BIOS splash for like, 10 seconds. how to fix

>>52847518

Startup finished in 6.247s (firmware) + 5.514s (loader) + 3.475s (kernel) + 1.542s (userspace) = 16.780s

I could reduce the loader time by removing grub as I only boot Linux on this machine.

File: 1438065888019.jpg (98KB, 600x480px) Image search: [Google]

98KB, 600x480px

>>52848416
Change wait time in BIOS settings.
>Reminder to read the sticky

4-5 seconds on botnet10 with a Samsung SSD (SATA, not M.2)

Basically the second my laptop display lights up when I turn the laptop on the grub menu appears. Then I press enter, and 2-3 seconds later my hardware is fully initialized and I'm at a login prompt. From there it's all about my typing speed and accuracy to login, which has nothing to do with boot time. So I'd say 3.5-4s from dead cold powered off to fully booted and ready to work.

>>52848483
>>52848128

4.3 seconds on NSAterminal10 with SSD

>>52848416
That's what I mean.
Asus "TWENTY PERCENT OVER CLOCKED" takes like 5 seconds.
But winblows takes 3

Do you count the time from the on button, mobo screen or a bootloader screen?
It's about 15 seconds from when I turn the thing on. Hackintosh, SSD.

>>52848391
in all honesty I'm pretty sure the HDD is dying and I don't care enough about the PC to replace it. The only thing I ever did on it was vidya gayems and I barely have time for that shit anymore. I just felt like blaming the botnet because dank memes.
>>52848400
Yeah that was the first thing I tried and it still didn't help me. It took disk usage from 100% to 99%.

5-10 seconds

win 7, g3260, bx200

>>52848457
nice meme, and I did. it's on 0 sec

>press power button
>wash face
>its on
I probably never sit waiting for it to boot

>>52848338
I am having the same thing with win 10.

5 seconds with my chromebook and able to instantly do shit after logging in

20-25 on my win10 desktop pc and up to 2 minutes before I can do anything

>>52848416
In your bios, check to see if there is a fast boot option or an option to bypass the RAM check and see if there's any options for disabling boot splash screens

Startup finished in 3.815s (kernel) + 1min 30.333s (userspace) = 1min 34.149s
I think my post time is also around a minute, it has to check all 24GB

>>52848782
That's because you don't have a ssd on your desktop

>>52847518

Startup finished in 12.643s (kernel) + 27.784s (userspace) = 40.428s

centrino duo 1.5Ghz
2.5Gb RAM
1T HDD ?rpm
Luks on lvm
Arch

>>52848518
you can check how long it took to boot so there's no need to guess

see >>52847723
>>52847653

>>52849033
not ssd btw

>>52847518
Less than what it takes me to grab some coffee

>>52847518
About half a second. I never shut down though. Suspending is king.

Like 40s to boot and then 1 min to be usable in Win7, you can hear the HDD loading things.

Then again the last time i turned my computer off was like 3 months ago so whatever.

4 seconds in Windows 10 with my Alienware :^)

Windows 7 and SSD: 18 seconds.

Unfortunately my bios screen flashes twice which lasts 10 seconds and I have no idea how to disable it or make it flash once.

Honestly the best part is instant shutdowns and no login lag, which would last several minutes on my old seagate.

>>52849994
I'm pretty sure the SSD or my RAM is fucked as well because the 'starting windows' logo occasionally hangs for 90 seconds.

Sandisk ultra2 128GB btw.

>>52847518
x220 running xubuntu >> 12 sec

desktop running botnet 10 >> 20 sec

macbook running osx >> 30 sec


Desktop is the one that boots more frequently because I don't leave it turned on. macbook hasn't been turned off in a month, same the x220.

Just replaced my HD with an SSD yesterday. Did not time it yet, but i'd say under 20 seconds most definitely. I think it's just a bit longer than your 7 seconds because i have multiple drives, some with different OS's, and maybe it scans them real quick or something. Login is absolutely instant. Didn't try video/audio exporting yet, but very excited to test it out.

I think my HD was the biggest bottle neck of my 12 core system. So this should be pretty sweet. But i want to get more RAM later too, currently have 24gb.

>>52849237
we can tell

>>52850114

Oh, and it's an 850 evo 500gb

MacBook has the same one, and it boots in under 10 seconds.

30 seconds on my 2000$ desktop running wangblows.
7 seconds on my 8 year old thinkpad.

0.4 seconds SSD Sata 3 + Arch

File: 1GHz Comp.jpg (342KB, 1536x1152px) Image search: [Google]

342KB, 1536x1152px

I'm using a fucking Phenom II from 2010

 
~/ » systemd-analyze 
Startup finished in 916ms (kernel) + 4.516s (initrd) + 1.583s (userspace) = 7.016s

>>52847518

    2min 42.275s mlocate-updatedb.service
         33.524s plymouth-quit-wait.service
         23.979s systemd-journald.service
         17.411s systemd-udev-settle.service
         17.023s firewalld.service
         13.073s cups.service
         11.168s dnf-makecache.service
          9.541s accounts-daemon.service

wtf even is this shit

>>52848525
4.17 on sandisk ssd plus 2 ®

>>52847518
>CURRENT YEAR
>Shutting down your PC, ever.
The only reason i can find are some programs that need a reboot to work properly. But even that's pretty rare in CURRENT YEAR.

>>52851399
Screenshot or gtfo

30sec windows 7, normal hdd, no updates of any program installed. everthing runs portable.

File: MyComputerIsKeepingMyRoomWarm.png (1KB, 824x15px) Image search: [Google]

1KB, 824x15px

I hibernate it at night in the summer.

╭─[email protected] ~
╰─ systemd-analyze
Startup finished in 753ms (kernel) + 1.757s (initrd) + 19.311s (userspace) = 21.822s

>>52847518
I don't remember the last time I didn't suspend.

File: fd.png (29KB, 646x593px) Image search: [Google]

29KB, 646x593px

>>52847518
I'm usually shutting it down and booting again like 6 times every day. eGPU unfortunately requires full restart to work.

>>52847518
Desktop (7200rpm HDD)
>2.707s (kernel) + 6.762s (userspace) = 8.469s

Laptop (SATA3 SSD)
>872ms (kernel) + 2.496s (userspace) = 3.368s

Both are Arch without any display manager, but 'startx' takes about 1.5 seconds then it's instantly useable

2.3 seconds, windows 8.1 on an m.2 ssd

it boots faster than my monitor takes to wake up. neat.

>>52847653
>Debian Testing instead of Stable or Unstable
What a fucking cuck jesus fucking christ.

Startup finished in 613ms (kernel) + 19.897s (initrd) + 6min 37.725s (userspace) = 6min 58.236s

Sometimes it takes 30 minutes.

File: scrot.png (277KB, 1919x1079px) Image search: [Google]

277KB, 1919x1079px

>>52851937
delivers

>>52849714
Dude, gtfo
Wrong board
>>>/v/

>>52847713
this

>>52847518
Windows 8.1 Boot Time : 5 Seconds
Windows 10 Boot Time : 7 Seconds

fucking windows 10 making me wait a whole 2 more seconds.

How do I check? Task manager is telling me the BIOS takes 0.0 seconds.

File: Capture.png (18KB, 624x435px) Image search: [Google]

18KB, 624x435px

>>52853522
my best is 1.4 minutes.

>>52848106
Confirmed australasian

>>52847713
It does for laptops.

My pc is slow as fuck thanks to 8 sticks of DDR4 and the memory validation that DDR4 requires every startup. Post times close to a minute

>>52847518

[w@x201 ~]$ systemd-analyze 
Startup finished in 2.515s (kernel) + 2.006s (userspace) = 4.522s

i usually just suspend anyway

3 seconds for msi bios screen then 5 seconds for windows loading before landing on desktop. This is from a cold start with windows 7 and an ssd along with a 4790k.

Win10

~60 seconds currently
Goes down to ~40 seconds when well maintained

11 seconds for my Win10Pro 64 on a SSD.

>>52847518
4 Seconds on M2 SSD.

>>52850098
>leave macbook on
>turn desktop off
wat

>>52847724
>7 minutes
Nigger what the fuck. Are you running windows off of a laptop drive from 1997?

>>52847518
probably like a minute and a half

>>52848550
U wanted to shill for mac

windows 8.1 probably takes about 40 seconds. i get about 530MB/s sequential read so i have no idea what the people on this board do to get it to boot faster, i assume sacrificing some kind of animal to the ghost of steve ballmer

i have xubuntu on both my laptops and it normally takes 20-30 seconds. one runs from a hdd and one from a usb3.0 drive (has eMMC internally so linux is a no-go on that)

20 seconds with Windows 10 on a 256gb 850 Pro SSD

>>52847809
I have that feature turned off and it takes maybe a second longer. usually boots in 7 seconds

File: st.png (37KB, 646x593px) Image search: [Google]

37KB, 646x593px

>>52850377
Do you boot via UEFI? Mine so slow

Startup finished in 2.152s (kernel) + 2.848s (userspace) = 5.000s

Most of time i dont turn off computer. MY bios is realy fast so you need to aadd to this 5s bios time that is about 2s

>>52859250
Fairly certain Windows only shows "Last BIOS time" if you boot from UEFI.

Startup finished in 6.331s (kernel) + 21.504s (userspace) = 27.836s

i have quite a few things start on boot

>2.925 kernel + 3.699 userspace = 6.625
On an ancient thinkpad X300 with a blazing fast 1.2GHz C2D low-voltage

Startup finished in 1.530s (kernel) + 1.756s (userspace) = 3.286s

>Startup finished in 1.893s (kernel) + 601ms (userspace) = 2.495s

My system is pretty average, why are your startup times so long?

>i5-4690
>8gb ram, 120gb ssd
>Debian testing

File: ：^ ).png (28KB, 769x504px) Image search: [Google]

28KB, 769x504px

In reality, it takes about 8 seconds.
1 second at bios (fast boot)
4 seconds loading windows
3 seconds logging in.

It's ready upon login, though some programs take a few seconds to start up afterwards.

>>52859705
>unironically using razer shit

>>52859809
Can we stop this meme anytime soon?
Can people actually be gamers with a need to have several buttons on their mouse?

>>52860252
I'm not a gamer but I have a ton of buttons on my mouse. I'll still never buy razer hardware or even touch their software though.

Windows 7 ~ 1 minute for the login screen.

>>52859705
How much ram do you guys with the crazy fast posts have? I have fastboot enabled, but I noticed that with heaps of ram (>16GiB) post starts taking aggges.

Startup finished in 4.983s (kernel) + 6.278s (userspace) = 11.261s
          5.278s exim4.service
          1.366s lm-sensors.service
           708ms dev-sda3.device
           462ms console-setup.service
           427ms keyboard-setup.service
           157ms ModemManager.service
           150ms networking.service
           125ms accounts-daemon.service
           114ms libvirtd.service
           102ms systemd-logind.service
           101ms NetworkManager.service
            99ms systemd-rfkill.service
            98ms irqbalance.service
            97ms systemd-hostnamed.service
            94ms systemd-timesyncd.service
            84ms alsa-restore.service
...

>>52847518

I don't know, about 10 seconds (cold boot).

Windows 7, 3770k, Intel 530 SSD

>>52847518
Boot time? Not really sure
Uptime? 7 days for my main server
10 days for my router

I've been modifying some things recently

>>52851894
I can't say I shut mine down but I've actually found hibernate to be useful. The server rack does enough damage to my power bill, I don't need anymore from an overclocked i7.

>>52847723
This is why I love systemd

>>52847518
Probably around 35seconds have to put in USB stick for key + enter password + again login

Arch on SSD:

>_systemd-analyze 
Startup finished in 910ms (kernel) + 2.253s (userspace) = 3.164s

Startup finished in 13.404s (firmware) + 6.113s (loader) + 2.526s (kernel) + 18.314s (userspace) = 40.357s

how do i improve this? is lightdm holding me down? is this a normal time for debian with xfce on a 7200rpm drive?

4-5 minutes on my win 7 machine.
The computer I had before took a good 15 minutes or more to boot so this is a godsend

Startup finished in 2.543s (kernel) + 12.052s (userspace) = 14.596s

Arch on SSD + HDD

9sec becuz my 290x vaporx needs to pre-heat itself to start working ayylmao

4690k, samsung 850 pro 256gb, crucial ballistix elite and z97x gaming 5

>>52863482
Loks pretty normal to me, for a non ssd.

>>52863482

>2016
>HDD

>>52863482
pls get a ssd as a system drive, you dont know what you are missing

File: meem.jpg (99KB, 400x400px) Image search: [Google]

99KB, 400x400px

>he fell for the meme of the meme ssd being a meme

>>52847518

Startup finished in 2.570s (firmware) + 3.210s (loader) + 5.376s (kernel) + 19.723s (userspace) = 30.881s

Thanks for reminding that I have to clean my system a bit.

>>52863482
do

systemd-analyze blame

and see what is taking time to load

>>52847518
3 seconds
Memepad x220 + Crucial SSD running Debian Testing x64

>>52863658
thats windows 7 x64 btw, with 3 ssd and 1 hdd, lots of clutter n programs/games installed

>>52854718
>just suspend
who doesn't? even 1s is a long time

35306ms

Is systemd-analyze reliable?
Can i trust this time?

>>52863996
no, its an backdoor

>>52863786
>

          9.715s exim4.service
          9.214s libvirtd.service
          7.136s ModemManager.service
          5.498s NetworkManager.service
          4.331s dev-sdb2.device
          4.193s avahi-daemon.service
          3.746s lightdm.service
          3.289s rsyslog.service
          2.659s ufw.service
          2.281s binfmt-support.service
          2.224s console-setup.service
          2.003s iio-sensor-proxy.service
          1.777s irqbalance.service
          1.775s lvm2-monitor.service
          1.753s ssh.service
          1.747s minissdpd.service
          1.566s polkitd.service
          1.434s systemd-logind.service
          1.213s systemd-udevd.service
          1.043s systemd-journald.service
           966ms systemd-fsck@dev-disk-by\x2duuid-BFC4\x2d1FC2.service
           900ms hddtemp.service
           892ms alsa-restore.service
           889ms gnunet.service
           845ms systemd-tmpfiles-setup-dev.service
           807ms networking.service
           742ms upower.service
           645ms systemd-modules-load.service
           640ms boot-efi.mount
           517ms dev-mqueue.mount
           485ms sys-kernel-debug.mount
           484ms dev-hugepages.mount
           463ms virtualbox.service
           429ms lm-sensors.service
           369ms speech-dispatcher.service

looks like lot of stuff i don't need, how do i remove the ones i don't need? virtualbox is not installed for example.

>>52864023
You can disable what you don't want to autostart during boot with

systemctl disable unit

. (Units can still be manually started.) If you don't know try search what each one is about to see if you do or don't need it.

6-8 seconds with Windows 8.1 and SSD.

File: Untitled.png (32KB, 792x600px) Image search: [Google]

32KB, 792x600px

>>52859250
>>52850377
AYY