The one thing they have yet to address: performance

[luke_f]

If people buy crappy 300$ hardware it's their problem. Surely they cannot expect nearly the same performance, compared to real up-to-date hardware. All these cheap devices use mechanical HDDs or very slow flash memory, which is both totally outdated technology by now. I just replaced my old SSD with the latest Samsung 850 Evo and man has my machine gained traction!! A complete startup (real startup using "Restart", no hibernation tricks) takes me to my desktop in 5 seconds!! With hybrid it's even faster.

The limiting factor for startup and performance is really the HDD now. It's not Windows anymore holding back the devices.

Windows could still use work regarding efficiency / power usage. Too much stuff going on in the background. Other OS are definitely better there. But my feeling is that performance and efficiency is not a priority for Windows 10. They have done a great job on that with Windows 8 already. Windows 10 is about user experience, platform unification, and enterprise needs. Everything else can come with future updates.

 

[dkediger]

i'm fairly sure you don't understand how hybrid start/shutdown works.
It kills everything up to the kernel, and only saves that. To make it simpler, think of it as going in hibernation just before the logon screen. Of course standard hibernation is way faster and resumes the system correctly.

i think you are misunderstanding the machines i'm referring to.

Hybrid sleep is referred on a machine, z87, i5 4690k, 8g 2133 ram, wd caviar blue.

And it's preferable to read a long defragmented file than a lot of smaller ones in any case- it's going to stress less the heads of the drive.

You specifically mentioned hybrid sleep, which is distinctly different than hybrid shutdown. Hybrid shutdown behaves as you describe - dump the User state and maintain an image of the System kernel in the hibernation file. Hybrid Sleep does, indeed, write the User state to the hibernation file, while the System stays suspended in Sleep mode.

Microsoft states that the default hiberfil.sys is sized at 75% of installed RAM, and when hibernation occurs, RAM contents are "compressed" in order to meet the smaller space. They also outline a way to expand that capacity, as well as a way to turn Hybrid start/shutdown off/on. Might be worth it to run a comparison over several shutdown cycles to see if there's a difference.

I would also look at using a startup config tool, like msconfig, Glary, etc and see if any third party services are having an effect.

 

[link68759]

You specifically mentioned hybrid sleep, which is distinctly different than hybrid shutdown. Hybrid shutdown behaves as you describe - dump the User state and maintain an image of the System kernel in the hibernation file. Hybrid Sleep does, indeed, write the User state to the hibernation file, while the System stays suspended in Sleep mode.

Microsoft states that the default hiberfil.sys is sized at 75% of installed RAM, and when hibernation occurs, RAM contents are "compressed" in order to meet the smaller space. They also outline a way to expand that capacity, as well as a way to turn Hybrid start/shutdown off/on. Might be worth it to run a comparison over several shutdown cycles to see if there's a difference.

I would also look at using a startup config tool, like msconfig, Glary, etc and see if any third party services are having an effect.

Just adding a detail- the way hybrid sleep works is it sleeps instantly, and several hours later the computer wakes up again to hibernate, so the sleep is instantaneous but your hiberfile.sys has not been populated until a user configurable amount of time has passed. I know this because last week my laptop kept waking up with the lastwake report saying "woke up to hibernate", but it had obviously failed to go into hibernation for whatever reason. Annoying, but fixed by a reboot

Windows might also hibernate instantly and thus be slow to sleep if you don't have waketimers enabled, someone test that theory for me.