Wouldn't it be great if our favorite IDEs showed a little yellow lightning bolt indicating suggestions for reducing the power-consumption profile of the code? Some of it could be obvious stuff (StringBuffer in place of string + string in loops, for example). But nonobvious stuff could be flagged too.
Of course, I hope the authors or others will try the same sorts of things on low-power mobile processors, and with workloads closer to the real world.
a. Gathering perf data in prod at scale
b. Aggregating it and mapping it back to source
c. Having that available within the IDE
Looks like youre working for a surprisingly clueful employer if they are doing all of the above.
I only open an exception to VS Code, because it is currently the best experience to edit Rust code.
Apart from being unreliable, bad design, it slows GC and instantiation by orders of magnitude, which I considered important, but they did not.
I added a comment about how uninstalling the Facebook app improves the battery life of a phone dramatically, that I deleted afterwards because it was too flamy.
I don't expect this to get fixed ever :(.
What causes divergence between energy efficiency and time complexity? I would expect both roughly scale proportionate to the number of instructions executed.