Linked by diegocg on Sun 13th May 2012 23:48 UTC
Linux Lennart Poettering, the author of systemd, has announced: "I just put a first version of a wiki document together that lists a couple of easy optimizations to get your boot times down to [less than] 2s. It also includes a list of suggested things to hack on to get even quicker boot-ups."
Thread beginning with comment 518005
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why do fast boot times matter?
by Neolander on Mon 14th May 2012 07:08 UTC in reply to "Why do fast boot times matter?"
Neolander
Member since:
2010-03-08

A while ago, I have tried to sum up in a blog post the reasons why I prefer to turn my computer off instead of putting it to sleep when I'm not using it. Maybe you would want to read that.

http://theosperiment.wordpress.com/2011/07/15/5-reasons-why-i-think...

Reply Parent Score: 2

Hypnos Member since:
2008-11-19

Thanks for the link. My responses:

#1 -- don't care. I use my laptop like my phone, always has to be at the ready.

#2 -- not sure. I've never had RAM fail on me despite 24/7 operation. It's true that constant charge/drain on a Li-ion battery is not good. On my Thinkpad I set the charge thresholds using the SMAPI interface and leave the laptop plugged in most of the time.

#3, #4 -- not really a problem in Linux

#5 -- this one is more interesting -- I will consider it.

Reply Parent Score: 2

Neolander Member since:
2010-03-08

#2 -- not sure. I've never had RAM fail on me despite 24/7 operation. It's true that constant charge/drain on a Li-ion battery is not good. On my Thinkpad I set the charge thresholds using the SMAPI interface and leave the laptop plugged in most of the time.

Well, the components which I have ever have to change late in a computer's lifetime, and thus consider vulnerable to aging, are...

-> Laptop batteries : Always, because most other computer components are designed to last more than 18 months.
-> Hard drives : From time to time, but these are not affected by permanent sleep since they are pretty much turned off.
-> Screens, RAM : Rarely but happens, especially to the cheap noname components that they put in commercial computers. Failing RAM especially is annoying because it is tricky to diagnose, though MemTest is helpful when it works.

#3, #4 -- not really a problem in Linux

On Linux, most background services are only restarted during OS reboot. So while their files may be updated, the running copy of the software isn't. Due to this, if you leave a computer in sleep or hibernate for months or years, you effectively take nearly the same security risks as if you disabled updates altogether (though "user" software will be kept up to date on its side if you regularly close it).

Linux also has its own issues with sleep and hibernation. Basically, some drivers can sometimes end up in a garbled state and freeze upon sleep and resume. If you can isolate which kernel module exactly is failing (in my case ath9k), you can ask the OS to unload it on sleep and reload it on resume, but this approach has its problems.

Edited 2012-05-14 17:16 UTC

Reply Parent Score: 1