4 ms·
Straight-line performance per watt is not the problem IMO. The problem is something along the lines of sleep/wake states and how MS + Intel can’t seem to get it
by D13Fd 4y ago
Straight-line performance per watt is not the problem IMO. The problem is something along the lines of sleep/wake states and how MS + Intel can’t seem to get it together to handle the times when the CPU doesn’t need to be working.
- duped 4y agoFrom what I've heard this is mostly on board designers and the complexity of how x86 handles the multiple levels of sleep/power state. Taking a conservative approach is done to prevent bricking devices on wake. I wouldn't blame MS for this. Linux has the same, if not worse, state.
- g_p 4y agoI think the root issue on sleep is Microsoft/vendor induced - this issue only really began when Microsoft introduced connected/modern standby, and started to incite OEMs to remove BIOS/UEFI support for S3 sleep. It seems unfathomable - maybe there is a valid reason for modern standby, but I've yet to find it. S3 resume is quick on a good laptop with good firmware. Modern sleep seems to drain the laptop battery quickly for some reason, and yet this has been going on for years now. Maybe standby drain isn't part of the Windows logo requirements and ought to be?