Click to See Complete Forum and Search --> : what is your boot time?
anmaxp
01-09-2004, 06:13 PM
Ok I just wanted to start a thread to find out how long does it take for your pc to get from the bios to your linux desktop?
i use fedora , so my pc takes more than a minute i guess
are we talking X desktop or just command prompt?
AndrewLubinus89
01-10-2004, 12:15 AM
Uh, I haven't tried with just prompt but everything including x and gdm takes 1:03 to start in rh. Haven't tested it in mdk.
mmills
01-10-2004, 12:53 AM
my boot time to KDE in mandrake 9.1 is aprox 60 seconds.
Wolface
01-10-2004, 01:27 AM
mine is 43 secs :D
Drago
01-10-2004, 01:45 AM
20-25 secs at max but i think it's lower (arch linux rules!:D)
My boot is pretty fast, I guess it's 30 secs or so.
carbon-12
01-10-2004, 02:45 AM
mines about 50 seconds.
andycrofts
01-10-2004, 02:58 AM
Can't remember...
Been so long ago... :D
But on my laptops about 2 mins before I get 'stable' usable desktop, assuming I'm lightning fast with username and password. Lots of company-specific bloat, and encryption on HDD.
Includes bringing up interface(s) and getting response from ntp server, dhcp, etc., etc. Much slower of course in standalone, because have to wait for above services to time out...
-Andy
MartinB
01-10-2004, 08:35 AM
16 seconds (Not including the POST / BIOS stuff, just the time it takes Linux on it's own to reach the login prompt)
bwkaz
01-10-2004, 10:31 AM
Hang on, I'll reboot and double check it for sure.
OK. From hitting enter at the grub prompt (grub takes maybe one tenth of a second to load ;)) to my login: prompt (runlevel 5 sucks :D), it's 15.9 seconds. I could cut a couple off of that by removing a few intentional delays in my boot scripts. (One of them used to be there to allow my USB modules to load without spewing a bunch of informational messages to the screen, only to syslog. That one isn't required anymore, because hotplug now loads up the modules with a reduced dmesg level so they aren't spewed at all. Another delay happens when I run sensors -s to program the values in /etc/sensors.conf into the sensors, then to run sensors once to make sure it flushes out its old limit values. This isn't strictly required either -- I don't hardly ever use sensors. That's about 4 seconds total of delays that don't need to be there: 3 for the USB stuff, and 1 for the sensors.) So it could be closer to 12.
From hitting enter after typing "startx" until I get a usable desktop with my three Eterms and a gkrellm on it, it's 12.5 seconds. I could cut a couple off that by disabling the nVidia logo, and a couple more by not loading a background pixmap right away, but frankly, why? When it's only 28 seconds total (plus login time and time to type "startx", plus the grub timeout of 5 seconds if I'm not sitting right there), what's the point? Sure, it could be 22, but 6 seconds isn't all that significant.
i've never timed it, and don't really care enough to bother. certainly less than 30 seconds and probably less.
30 to 45 seconds max. Vector Linux :)
mdwatts
01-10-2004, 02:41 PM
My main home pc takes over a minute due to the hardware I have... specifically the Promise IDE Raid Controller which takes a while to check the attached HD's.
The main work pc takes 30 seconds or so.
hard candy
01-10-2004, 02:45 PM
One time I got both boots on (untied) in about 3 seconds, course the house was on fire at the time.
Ohhh! Bon Bon just told me your talking about COMPUTER boot time- about 52.5 seconds if the wind is blowing the right way.
Seph64
01-11-2004, 04:07 AM
It takes my system about 27 seconds from BIOS to the login prompt (CLI of course).
deathadder
01-11-2004, 08:12 AM
From the BIOS check to a login prompt its 27sec's
Onzic
01-11-2004, 09:17 AM
about 7 min (stops at "Starting hardware scan on boot" and sits for 6 min doing nothing). Im using M$ xp at the momment cause I cant be arsed to wait.
1000mh P3, 128mb ram, 80Gb harddrive, dont have a clue why it takes so long
rocketpcguy
01-11-2004, 01:27 PM
15 seconds, end of bios to the desktop with everything loaded, minus the time to enter the name and password
bwkaz
01-11-2004, 05:09 PM
Originally posted by Onzic
(stops at "Starting hardware scan on boot" and sits for 6 min doing nothing). You can probably disable whatever service is doing that.
Take a look at the tools your distro provides to manage what stuff starts up at boot time -- RedHat, for example, uses /sbin/chkconfig from the command line (and a couple of GUI programs). I think KDE still comes with a program to edit your bootup scripts (ksysv I think...), which will work unless you have Slackware (or another BSD init distro).
jedthehumanoid
01-11-2004, 05:57 PM
Originally posted by Drago
20-25 secs at max but i think it's lower (arch linux rules!:D)
hell yeah, i totally dig arch also. my box boots up to kdm in about 35 seconds. i've tried a hell of a lot of distros and the only one that seems to be as fast is gentoo and i personally found gentoo to be a pain in the ***. honestly, the only thing i don't like about arch is that its not more recognized!!
nabis
02-14-2004, 09:27 PM
P4 1800 MHz 384 MB RAM Slackware 8.1
5 seconds Lilo, 15 seconds to the login prompt (with nfsd sshd, no httpd). Not bad :)
JohnT
02-14-2004, 09:42 PM
24 seconds to the KDE desktop. It hangs at adsl connection.:D
sploo22
02-17-2004, 10:28 AM
For comparison, my new 2.4 GHz WinXP laptop takes about 2-3 minutes to get to the login prompt, plus another 10 minutes after login before the hard disk stops grinding and the system's actually usable.
Let's see someone top that :p
Icarus
02-17-2004, 10:39 AM
"Four score and seven years ago our fathers brought forth..."
or something like that :)
hard candy
02-17-2004, 11:28 AM
Well, if my machine boots up in 24.3 seconds and then shuts down in 26.5 seconds--------> that means I have a negative 2.2 seconds boot time. Correct?
So by that measurement, I currently have the fastest boot time posted so far, which means I win what? I hope its something valuable.
But also, if we rarely have to shut down according to the threads about "Post Your Uptime", then boot up time has very little relevance to actual computing work. Which is more important----> "Uptime" or "Boot Up Time" ? They're sort of mutually exclusive in my way of thinking, you can't win one without losing the other. :confused:
JamminJoeyB
02-17-2004, 11:40 AM
Hard candy you beat me to it. A fast boot time is nice, but uptime and stability to me are paramount. When I want to get something done I don't want to have to worry about rebooting becuase my MS OS has been running for a couple of days.
Just to stay on topic, 30 secs from pressing the power button to gnome desktop. Found this out last week when the power went out for an hour. Screwed my uptime though.