Hibernate mode Vs Sleep Vs Hybrid sleep.

[Bill_Bright]

But you cannot deny it's shortcomings , even though ultimately they are unavoidable.

Nothing is perfect. I am just saying because sleep mode might not work properly 1 time out of 1000s, that's no reason to disable it. That's particularly true on the newest version of Windows with the latest hardware.

in W7 the hiberfil.sys was 6GB and after i deleted on W10 i got 20GB free space, is it the hiberfil.sys file bigger on W10 than on W7

It depends on many factors, including what you have running in memory and how much RAM you have installed. But since W10 is designed to boot and come out of sleep mode much faster than W7, then it makes sense the file would be larger.

Let's also remember W7 is nearly 8 years old. The average size disk on new computers is much larger than 8 years ago too.

 

[Shihab]

Sorry, but that makes no sense. First, hibernation was indeed developed for notebooks - so when you close the lid, you can resume exactly where you left off. Yes, you can use hibernation with a PC and you can use hybrid mode on a notebook But hybrid mode was developed for the PC.

Second, if a user suffers from frequent blackouts they should definitely be using a good UPS with AVR. Note I've lived in Tornado Alley for the last 28 years so I have some experience with that. But more importantly, if a user suffers from frequent blackouts and they don't use an UPS, they should be saving their work and "gracefully" shutdown the computer, not put it in sleep mode.

Lastly, hybrid mode is called hybrid mode because it is just that, a mixture of modes. In hybrid mode, data stays in RAM (in a low voltage state) for faster wake times. But in hybrid mode, a full hibernation file is also created in case the user (or Mother Nature) decides to remove power completely.

I'm starting to lose track of what we're disagreeing on. I can't say what was on the mind of whoever designed the technique in the past, but today it is a tool available to any supporting platform where the users need it. Hybrid sleep is functionally a suspension to disk without clearing the ram, at its core it is a hibernation. Arguing which method is for which platform is -with all due respect- a waste of time. I would agree to the argument that Hybrid sleep is more versatile than simple hibernation, though, but that doesn't make hibernation a non valid method of suspension on desktops. And if someone intended for long down-times or expected power loss, the differences between hibernation and hybrid sleep become inexistent.

For the frequent blackouts part, we have to consider the scope of the issue here: whoever opts to use any suspension method, hibernation, sleep or hybrid sleep, does so explicitly to avoid shutting down the computer (for whichever reason they wanted). Anecdotal example: I'm off to work in the morning, but I do not want to close all the software and web pages I have open (and they can be many) and restart them later, so I have the choice of either sleep or hibernate (or hybrid methods), but with any S state less than 4, I run the risk of a blackout forcing me to what I avoided shutting down for, so I elect to use hibernation (or hybrid sleep, of which the hibernation part is what's needed).

A UPS is indeed a must have, but alas, not all of us live in the first world!

Pretty sure your point is correct.
Anything written to volatile memory is wiped once the computer wakes afaik. I've seen threads before about users complaining of RAM usage increasing after a computer wakes from sleep mode and as far as I know it's entirely anecdotal.

VRAM isn't wiped post-wake up, per se. The only way to wipe the entire memory is relieving if of power. Hibernation does have that effect in the suspension process (going into hibernation), upon waking up it repopulates the memory with what was occupying it before turning off (though I don't know if it was actually this simple).
What was I referring to in my previous post is Windows' memory manager's functionality. When a process is closed (eg: Alt+F4ed the main window, killed in task manager, etc), all its memory heap is then freed up for other processes to use. So, any memory that is used when a computer wakes is for actually running processes, waking up won't reserve memory for anything else (other than hardware, I guess?)

Computers can be weird. I once had a recurring issue with Microsoft's Security Essential where it starts eating up all my ram after waking up from sleep. And I'm talking about 20GB of physical memory! Still don't know what caused that bug though. Couldn't reproduce it in later Windows installations on the same hardware either.
And don't get me even started on those cheap Chinese hardware!

 

[FireFox]

It depends on many factors, including what you have running in memory and how much RAM you have installed. But since W10 is designed to boot and come out of sleep mode much faster than W7, then it makes sense the file would be larger.

Let's also remember W7 is nearly 8 years old. The average size disk on new computers is much larger than 8 years ago too.

Fair enough.

I have enabled the hiberfil.sys again.

 

[Slizzo]

In the age of Windows 7, 8, 8.1 and now 10, plus availability of SSDs and now NVMe drives, I shut down my PC.

Takes around 15 seconds from push of power button to a usable desktop on my home machine, so I shut it down when I'm not using it. And now that MS has added install updates and shutdown back into Windows 10, it's all as it should be.

 

[Bill_Bright]

akes around 15 seconds from push of power button to a usable desktop on my home machine, so I shut it down when I'm not using it. And now that MS has added install updates and shutdown back into Windows 10, it's all as it should be.

Good points, for sure. I guess the laziness part of me sees tapping the space bar to wake up my computer is easier than reaching over to press a power button.

That said, even though I am more or less retired now, and what work I do is out of the home, there are times when I am called away from my computer for a little while - even if to just sit on the pot! And then I do like to resume (or see) where I was when I return - even if hours later, or the next day.