There are other topics dedicated to troubleshooting issues with suspend, however, I believe, in my case, it works as intended, but… I am not sure it is good enough.
I will be focusing on Linux since this is what I know, but, based on what I read in other topics, the situation on Windows is similar.
Here is a specific data point:
- Last night, my laptop was suspended for
39930seconds (roughly, 11 hours and 5 minutes). - Of those, it spent
39923in hardware sleep state, that is, almost the entire time (the difference is 7 seconds, which, by the way, is pretty large – normally it is more like 2 seconds, and I am not sure what was different this time). - The battery went down from 70% (2744 mAh) to 62% (2460 mAh).
This gives us a rate of 0.65% (25.6 mAh) per hour of sleep. Elsewhere on the forum, I saw people report the rate of around 1% per hour on Windows, so, comparable.
Now, here is the question that I keep asking myself: is this good, merely acceptable, or bad? E.g. this means that the battery will be essentially empty after 6 days of sleep. My personal feeling is that this is sort of acceptable, but I would definitely wish for much more.
Microsoft seems to agree! Their Modern Standby Duration Test says:
Systems that support Connected Standby are recommended to drain less than 5% of system battery capacity over an 16 hour idle period
If I scale the result of my experiment, I am getting the drain of 10.4% over 16 hours – more than twice as much as recommended and it is not even Connected Standby as in their test.
So, where do we go from here? @Mario_Limonciello’s amd_s2idle.py script doesn’t find any issues with my system and, given that it spends pretty much the entire time in the deepest hardware sleep, I suspect there is nothing I can really do to improve the situation on my own, at least not on the software side.
Should I be looking for more power efficient hardware parts? Is there anything that Framework can do to reduce the drain? Can AMD help?