Why Do Computers Take So Long to Boot Up? 975
An anonymous reader writes "Computers take too long to boot up, and it doesn't make sense to me. Mine takes around 30 seconds; it is double or triple that for some of my friends' computers that I have used. Why can't a computer turn on and off in an instant just like a TV? 99% of boots, my computer is doing the exact same thing. Then I get to Windows XP with maybe 50 to 75 megs of stuff in memory. My computer should be smart enough to just load that junk into memory and go with it. You could put this data right at the very start of the hard drive. Whenever you do something with the computer that actually changes what happens during boot, it could go through the real booting process and save the results. Doing this would also give you instant restarts. You just hit your restart button, the computer reloads the memory image, and you can be working again. Or am I wrong? Why haven't companies made it a priority to have 'instant on' desktops and laptops?"
hum (Score:4, Informative)
boot time (Score:4, Informative)
If you want a quick start, just use sleep mode. Takes very little power and you're up in seconds.
Hardware and Security (Score:5, Informative)
First, let's say that you upgrade some hardware. There will be no way for the OS to know that there's new hardware unless it goes through the hardware detection and configuration stages of bootup, which is what takes most of the time. Worse, if it doesn't do this, the system will probably just crash, as the memory image loaded will have the wrong set of drivers installed and they'll be pointing at the wrong set of hardware addresses.
Second, and this is more of a recent issue, there is a lot of work that's going into randomizing memory addresses to increase security. In the event of a security hole, randomized memory addresses make it far more difficult to take control of the machine as a hacker, virus, or worm can't use a hard-coded memory address during the attack. With a pre-built boot-up image, the memory addresses will not be randomized, which defeats a lot of the gain of this security benefit.
That said, you could just use hibernation on your computer. That is essentially the same thing as what you're asking for. A desktop is just as capable of sleeping or hibernating as a laptop is. The only thing is, if you want to make any hardware changes, you must remember to turn on the machine and do a complete shutdown first.
Also, there are companies who are focusing on bootup speed. In fact, every major Linux distro has been focusing on it for the last year or two. It's unfortunately just not that easy to speed things up without sacrificing stability or functionality.
instant booting over the horizon (Score:2, Informative)
personally, i think this is a fantastic idea. i really love the fact that my powerbook can go from sleep mode to on in under a second. however this takes quite a bit of battery power to accomplish. wouldn't it be much better if they wrote out the memory to flash when the lid closes? then instead of sleeping, you'd be able to shut down and re start very quickly.
Is 3 seconds not fast enough? (Score:2, Informative)
http://linuxbios.org/index.php/Main_Page [linuxbios.org]
The truth is, this subject is an old one. The main answer is that it just takes time to get a DHCP lease, set up a few dozen services, and generally get all of the "junk" you need up and working without crashing the system. If your main complaint is Windows XP there are a few tuning guides that can reduce your boot time dramatically.
Re:Windows does a lot of writes when booting (Score:3, Informative)
Pagefile initialization is my guess.
Re:IBM's "Rapid Resume" (Score:2, Informative)
Re:Hibernate (Score:3, Informative)
Obviously, you've never used a Mac. Get one, and all the "suckitude" (that's related to power management, at least) will magically disappear.
Re:Hibernate (Score:5, Informative)
Re:Hibernate (Score:2, Informative)
Re:hum (Score:3, Informative)
Re:Hibernate (Score:5, Informative)
Re:fast booting TVs ? (Score:3, Informative)
Embedded computers [embeddedarm.com] may be what you are looking for.
Re:hum (Score:5, Informative)
Re:fast booting TVs ? (Score:1, Informative)
Re:Errr.... (Score:4, Informative)
Because coffee takes that long to brew (Score:5, Informative)
Linux on an embedded system configured for fast booting(without plug and play peripherals etc) can boot in 2 seconds or so.
i-RAM (Score:5, Informative)
According to Anandtech, booting with the i-RAM into Windows XP takes 9.12 seconds. [anandtech.com]
Re:Errr.... (Score:5, Informative)
No, they do not "keep the tube warm". Yes a TV might draw a few watts when in "off" mode due to the power supply for the digital logic section always being on. But just about every CRT based TV or monitor I have seen, except for maybe some real high end broadcast equipment, takes a few seconds for the tube to come up.
You definitely weren't around in the 60's and mid 70's when we watched the tube warm up and the displayed image grow from a small dot to the full size of the screen. Sometimes it would take 20 or more seconds before the picture stabilized. When you turned the TV off you got to watch the "boot" process in reverse as the display shrunk to a dot. It was a big deal when we got "instant-on" TV's.
Well yes, TVs used to take longer to fully power up, and didn't have dampening circuits to prevent CRT display after being turned off. They where basic fully analog devices, there was no logic that prevented the display of an image when the CRT was not yet in an operational state. In the 60's they would have been vacuum tube based (as in the whole TV, obviously a CRT is a vacuum tube) and taken a long time to fully warm up, and needed adjustment and retubing on a regular basis. In the 70's they would have been transistor based, and would have come up much faster, how ever they would still be fully analog and subject to the same power up and power down effects.
Modern TV's have digital control sections that can compensate on the fly for variations in the analog sections of a CRT display, and higher performance switching power supplies and fly-back circuits that come up to operating voltage much faster. But you still have at least a short wait for the CRT to come up, they are not kept on warm idle of any kind. At least not in any displays I have worked on.
I know this is probably getting off topic, but your post was marked +5 informative yet has miss information in it. Having worked on many CRT displays I just wanted to point out that the CRT is definitly not kept on any kind of warm stand-by, none that I have ever seen any way. What you are describing sounds similar to the stand-by mode in most guitar tube amps, where the heater filaments in the tubes are kept on to keep the tubes warm but the rest of the amp is powered down. I am not aware of this being done in modern CRT displays. Seems to me that if you did this it would dramaticaly shorten the CRT's life span, if the heater filaments were on 24x7x365. Someone correct me if I am wrong...
Linux BIOS Project (Score:0, Informative)
I'm suprised that no one has mentioned the Linux BIOS Project [linuxbios.org] yet.
From the page:
Re:Errr.... (Score:3, Informative)
Re:hum (Score:5, Informative)
Re:Errr.... (Score:2, Informative)
Re:hum (Score:4, Informative)
There is one issue I had at one point which is that my nVidia video drivers would BSOD on resuming, but updating them fixed that and I'm pretty sure they've fixed it completely in their newer cards.
Re:fast tuning TVs ? (Score:1, Informative)
It gets worse with the HD signals, especially moving to the newer encodings (MPEG-4), as audio and video may be separated by up to 5-10 seconds in typical broadcast streams.
I suppose it's solvable if you have spare tuners doing pre-tuning, but that starts bumping the manufacturing cost and chip or board design costs up. There's not a huge incentive to throw the additional hardware (and resulting complexity) at it. And that would only fix tuning up/down, not entering a channel number. And if you flip too fast, you'd be right back waiting on the sync issues.
The reason it can whip through channels when scanning is because it doesn't need any audio/video sync, it just needs a valid signal.
One of the joys of going digital...
S3 Standby (Score:4, Informative)
- 'Hibernate' takes about 20 seconds
- S3 Standby takes about 6 seconds.
One catch is that by default most systems use 'S1' mode for standby, which keeps the machine semi-alive including the CPU fan, power supply fan, etc. You can often go into the BIOS, change the default standy mode to 'S3' -- this will shut down the entire machine (including fans, etc.) but keep proviging a minimal power charge to the RAM in your machine so it won't lose its contents.
Since all the content remains in RAM that way, your machine will behave the same as if you did a hibernate, except it doesn't have to spend the additional ~25 seconds writing everything to disk first when you shut down, and also doesn't have to spend that time to read it back into RAM on bootup... Resulting in the ~6 second bootup time.
(While it takes some power for the RAM to keep its information, it is negligible compared to a complete shut down, since any modern PC still provides some power to the motherboard after it is 'powered off'. Case in point: See the LED on the main board indicating the power status on a machine that's supposedly turned off)
It's been a long time since I truly shut down my PC.
Note: the one catch is that if you do lose power to your machine while it is in standby mode, any contents that were in memory at the time will be forgotten again, and it will do a 'full' bootup next time you start. Hibernate doesn't have that problem, but takes significantly longer to shut down and boot up.
That bug is fixed. (Score:2, Informative)
Download and install to fix (you don't even have to ring PSS any more!) IMHO, this is an update they really should push out using Automatic Updates. (They probably will when the next security bug is found in the kernel.)
Re:boot time (Score:1, Informative)
I'm fairly certain that it's all a gimmick to put eyes on various brands. The hardware spin up, with one exception (certain drives) isn't hardly noticeable for humans, things happen on the long side on the order of a milli or 2.
Once you get in to kernel space and then user space there are some distinct things that could be done differently. Linux has a highly linear boot process for starters, that's potentially a fairly low hanging fruit, although you have to attack it in an intelligent manner. XP does some intentional fragmentation so that the pre-reading reads more stuff in to memory before it's needed. OS X pretty clearly spins off a bunch of threads and tries to very quickly get a log in prompt on the screen while a lot of the boot takes place after that.
11 seconds.. (Score:3, Informative)
I agree with the parent that there were sets where the filaments stayed on all the time for an "Instant-On" effect. Actually it was an always-on situation, but the B+ and high voltage wasn't applied until the set was "turned on". See http://www.repairfaq.org/REPAIR/F_tvfaqd.html#TVF
Re:hum (Score:2, Informative)
My linux laptop [rdegraaf.nl] takes 3 seconds to recover from 'Suspend to Memory'. (Link provides setup of hibernate and suspend_to_memory in Debian Etch on Dell Inspiron 1150).
Re:They have instant coffee now. (Score:2, Informative)
Nobody liked EISA.
Re:hum (Score:2, Informative)
Can be a problem in areas with unreliable power... (Score:2, Informative)
I don't much care about the downtime, but clients are faced with an outage of several minutes every time the server so much as reboots. I'm sure everyone here knows how people get when there's a 5 minute delay before they can start repeatedly (and optimistically) clicking the 'Check Mail' button. I'm sure they'd love the faster boot times
I don't relish the idea of populating a 16GB hibernation file - even on arrays of SAS drives. It might be easy to trivialise this question in a workstation context, but it has its relevance.
Re:How about instant OFF? (Score:5, Informative)
It's called "auto end task", and it's just a couple settings in the Windows registry. I've been using it successfully for a VERY long time now, and it works exactly as you'd want:
http://www.winguides.com/registry/display.php/199
If the program doesn't end (30 seconds) after it gets the kill signal, it gets killed without requiring you to be there to hit the button.
Re:Flash is just slow (Score:2, Informative)
The SanDisk Ultra IV cards are another example. They do about 40 MB/s. It's basically a RAID stripe across the internal flash chips.
Re:Windows does a lot of writes when booting (Score:2, Informative)
That's perhaps one cause of your filesystem usage increase.
Re:10K RPM LAPTOP DRIVE? LOLZ... (Score:4, Informative)
Or maybe you are.
--S (not that you'll find SAS in laptops, but hey, this is slashdot.)
Re:hum (Score:2, Informative)
Re:How about instant OFF? (Score:2, Informative)
Re:hum (Score:5, Informative)
And if you really want to speed up the bootprocess on some system have a look at the linuxbios project, if you mainboard is supported that is.
And some hints on how to speed up the bios "boot":
- Hard-configure the HD's you have in your system and deactivate any unused master/slave positions.
- If running PATA make shure master/slave is connected to the correct position on the cable and use the jumper to set it to master or slave instead of autodetect.
- Activate fast-boot
- Disable anything you dont use on the mainboard, if running linux check if you can disable IDE controllers you dont use for booting, some might still be usable after booting the OS.
- Activate fast-boot, on a warm-boot there are alot of tests that can be skipped.
- If you have any bootable cards in the system disable their boot-bios so they dont have to be scanned during the POST.
Just a few hints.
That's rediculous (Score:3, Informative)
I use then when writing auto-install scripts. For each app that tries to autostart (which is absolutley unnacceptable for any application to do) I find out how that particular one does it and disable it after the install/upgrade.
Re:hum (Score:5, Informative)
Or linux with 'init=/bin/sh'. Only takes a couple of seconds on my machine.
Re:hum (Score:3, Informative)
All of the programs that automatically run at startup show up under one of three places:
1. Registry: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru
2. Registry: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru
3. Startup folder in Start menu
QuickTime's entry is under the first.
Apple (Score:2, Informative)
They have. It's called the Mac.
Seriously, I had heard it before, but it was still astonishing to watch when I got my MacBook Pro this year. I was used to long boot times in both windos and Linux. I was used to long times going from hibernate and even sleep to activity.
OSX boots in less time than XP on the same hardware takes to awaken from hibernate. When it's sent to sleep, OSX is back before I've opened the lid completely. It's not quite instantaneous, but it's as close as I need.
OSX still needs to do a bunch of things at boot, and after login, and there is certainly the possibility for caching (as you suggested) or other speedups. I'm sure they will happen, because as I see it, Apple is currently the only company that actually cares about this stuff.
Re:hum (Score:2, Informative)
Re:10K RPM LAPTOP DRIVE? LOLZ... (Score:3, Informative)
2.5 inch form factor does not automatically mean "laptop drive".
Please show me a laptop that uses SAS instead of SATA or PATA.
Re:hum (Score:2, Informative)
OK
XP - Cold boot: 75 seconds
XP - Power off: about the same
XP - Hibernate: 0 seconds (just close the lid)
XP - Wake up : 9 - 10 seconds (includes re-establish wireless connect)
OpenSUSE numbers are close except that suspend to disk (or ram) crashes every time. Never powers off, kills the battery. So in the end I have to do a longer cold boot process every time I use the machine, plus wait a minute or so while it powers off (because I keep the laptop in a case, just walking away while it powers off isn't a choice).
All that said, in XP I can plug/unplug accessories, USB devices or whatever while it's suspended and it detects the change just fine. Toshiba must have made a deal with the devil to make S4 work so well on this machine. Maybe now that Novell made a deal with the devil, OpenSUSE will suspend just as well.
I may try OpenSUSE 10.2 today.
Microsoft Bootvis (Score:3, Informative)
Re:hum (Score:3, Informative)
Or, just get Mike Lin's tasty startup control panel [mlin.net].
Re:hum (Score:3, Informative)