

Battery Historian is one of them.īattery Historian is a tool developed by Google, launched in 2016, which allows one to analyze the behavior of a phone and more precisely to review information and events related to the battery. However, there are tools that can complete the analysis of the behavior of the battery and the phone. Several years of research and innovation that allow us today to offer a unique product to simply measure the energy data of smartphones. How to analyze the behavior of my smartphone with Battery Historian?Īt GREENSPECTOR, our R&D teams have been working for several years on the energy measurement of smartphones. Any component solicited consumes energy, monitoring energy consumption will detect over-consumption of resources.įor more information, we invite you to read our article Why you should measure the energy consumption of your software?. Our approach at Greenspector is different, we propose to use energy as a more reliable metric. Indeed, the current platforms are heterogeneous: CPU, GPU, Radio, multiple interfaces… It’s therefore complex to follow the current performance of these platforms and it’s necessary to use various and complex profiling tools. The problem is even more present in mobility. Indeed, a high CPU rate doesn’t necessarily mean that the CPU is requested and conversely a low CPU could hide overconsumption from another cache. We have observed this phenomenon through our R&D. Brendan Gregg even concludes that this problem will get worse with the acceleration of processor speed. It’s therefore necessary to use more advanced tools to analyze what happens in the lower layers of the code. For instance, a busy CPU doesn’t necessarily indicate that the CPU is busy doing calculations but is waiting for information. This is an opportunity for us to revisit what we have been pushing for a long time: How to measure performance and resource consumption reliably?īrendan Gregg explains that the CPU rate can indicate false information. In his Upscale 2018 presentation last march, Brendan Gregg, senior performance architect at Netflix, explains why the CPU isn’t a good metric for measuring performance.īrendan Gregg, senior performance architect at Netflix”Įveryone uses %CPU to measure performance, but everyone is wrong
