3 ms·
> The point is rather that curl now uses less CPU per byte transferred, which leaves more CPU over to the rest of the system to perform whatever it needs to do.
by 0xcde4c3db 10y ago
> The point is rather that curl now uses less CPU per byte transferred, which leaves more CPU over to the rest of the system to perform whatever it needs to do. Or to save battery if the device is a portable one.
Does anyone have a general sense of how these kinds of efficiencies translate to real-world battery life? I understand that the mechanisms (downclocking/sleeping the CPU) are there; I'm just curious as to how much it actually moves the needle in a real system.
- maccard 10y agoNot sure in hard numbers, but mobile processors are designed to work this way - do a small amount of work at full power and then sleep.
- zkms 10y agoRace to idle~
- 59nadir 10y agoIn any one single instance it's not that interesting, but considering probably half (if not more) of the stuff you interact with uses libcurl, it adds up to a lot.
- exDM69 10y ago30℅ less CPU use is roughly 30℅ less energy usage. The CPU will power down when it's done. Downclocking has negative impact because the CPU needs to be powered up longer and it is leaking current all the time it is not powergated.