It can be if you run linux and throttle the chips. Even my older G14 last a long time, as the AMD SoCs are great, it can run fanless throttled down, and it just has a straight up bigger battery than razor thin Macs.
But again, it’s just not configured this way in most laptops, which sacrifice battery for everything else because, well, OEMs are idiots.
Current gen MacBooks have massive batteries. The MacBook Pro 14 inch is 70-73Wh, same as your G14, and the 16 inch MBP is 100Wh, the legal limit to take on an airplane. Even the 13inch air, apple’s thinnest and smallest, is still 52Wh.
I don’t, I just run stock. I run an E495 and get something like 3-5 hours battery life, depending on what I’m doing, and after a few years of ownership, I still get around 3 hours battery life.
What specific driver and linux tools do you use to throttle your CPU?
Also throttling often produces the opposite result in terms of extended battery life as it likely takes more time in the higher states to do the same amount of work whereas running at a faster clock speed, the work is completed faster and the CPU returns to a lower less energy using state quicker and resides there more of the time.
I would be interested to hear your results. Have you done any tests comparing a throttled versus throttled system with the tools you are using?
On my G14, I just uses the ROG utility to disable turbo and make some kernel tweaks. I’ve used ryzenadj before, but its been awhile. And yes I measured battery drain in the terminal (but again its been awhile).
Also throttling often produces the opposite result in terms of extended battery life as it likely takes more time in the higher states to do the same amount of work whereas running at a faster clock speed, the work is completed faster and the CPU returns to a lower less energy using state quicker and resides there more of the time.
“Race to sleep” is true to some extent, but after a certain point the extra voltage one needs for higher clocks dramatically outweighs the benefit of the CPU sleeping longer. Modern CPUs turbo to ridiculously inefficient frequencies by default before they thermally throttle themselves.
It can be if you run linux and throttle the chips. Even my older G14 last a long time, as the AMD SoCs are great, it can run fanless throttled down, and it just has a straight up bigger battery than razor thin Macs.
But again, it’s just not configured this way in most laptops, which sacrifice battery for everything else because, well, OEMs are idiots.
Current gen MacBooks have massive batteries. The MacBook Pro 14 inch is 70-73Wh, same as your G14, and the 16 inch MBP is 100Wh, the legal limit to take on an airplane. Even the 13inch air, apple’s thinnest and smallest, is still 52Wh.
I don’t, I just run stock. I run an E495 and get something like 3-5 hours battery life, depending on what I’m doing, and after a few years of ownership, I still get around 3 hours battery life.
What specific driver and linux tools do you use to throttle your CPU?
Also throttling often produces the opposite result in terms of extended battery life as it likely takes more time in the higher states to do the same amount of work whereas running at a faster clock speed, the work is completed faster and the CPU returns to a lower less energy using state quicker and resides there more of the time.
I would be interested to hear your results. Have you done any tests comparing a throttled versus throttled system with the tools you are using?
On my G14, I just uses the ROG utility to disable turbo and make some kernel tweaks. I’ve used ryzenadj before, but its been awhile. And yes I measured battery drain in the terminal (but again its been awhile).
“Race to sleep” is true to some extent, but after a certain point the extra voltage one needs for higher clocks dramatically outweighs the benefit of the CPU sleeping longer. Modern CPUs turbo to ridiculously inefficient frequencies by default before they thermally throttle themselves.