On Thu, May 17, 2012 at 10:27:55PM +0200, Reindl Harald wrote:
>> i live in the world where someone starts his work in the
>> morining and powers on his computer once each day and
>> have all other machines running 365/7/24
>>
>> waking up from suspend to disk takes much longer as a cold start
>
> Can you provide some data to back this up? When I suspend my laptop it
> is far, far quicker to restore than a cold boot.
yes
Okay, I was asking you to actually provide that data, Reindl. ;)
> A suspend-to-usable operation is on the order of seconds
reading 16 GB RAm image in seconds?
not with slow disks
Yep. My laptop (Lenovo Thinkpad W510+) goes from suspend to running in a
few seconds. Hibernate's been broken in F17 for me so no stats there ATM
(which is why I'm interested in this thread).
> A cold boot is 10s of seconds.
currently 25 seconds including a lot of services
not used on a typical end-user machine
Not so quickly for me. Granted my swap and home partitions are
encrypted, but the password entry is hard a second or two during the
boot process.
>> and even if this is not interesting my expierience with
applications
>> and services having open network connections is that it sucks if they
>> are woken up in another network
>
> The machine should be able to handle it like any other interruption to
> networking (network down, switching APs, etc.). If it doesn't then
> that's a separate problem to be solved.
depends on your environment
if you are connected to a lot of LAn services and wake
up the machine on another location where they are all
not available or have different IPs it is not funny
Still, that's an issue separate from hibernating or suspending a
machine that should be handled similar to any other network interruption
scenario.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/