Hello,
Does anyone know of any way/means to measure/inspect how much load an app puts on the device ?
P.s. found the following post, which does not seem to have any replies
Hello,
Does anyone know of any way/means to measure/inspect how much load an app puts on the device ?
P.s. found the following post, which does not seem to have any replies
That was back in 2017 or 2018 if I recall.....
No need for a beer....
Already sent one your way
for the sake of performance calculations are only performed when onUpdate - upon invocation (every 1sec) - detects one or more of the following:
- location is available for first time since startup; in this case both sunset/sunrise are calculated
- either lat/long changed by more than 1-degree (compared to what is cached in the View-class from last successful retrieval from Toybox.Activity.getActivityInfo().currentLocation); in this case both sunset/sunrise are calculated (1-degree is about 4-5 min diff in sunrise/sunset times)
- either already-computed sunrise/sunset 'becomes past' (i.e. current time 'moved on' such that it is > sunrise or sunset); in this case only the 'past' one is re-calculated
still one could argue these sunrise/sunset calculations are a lot of heavy lifting for a poor wristwatch CPU built and designed for low battery consumption, and which is typically expected to simply/for the most part only perform drawing.
not to mention even when all conditions above are false there is calc work involved just to determine that (every 1sec: get cur coords and compare to cached + compare cur date/time to cur sunrise/sunset)
Would it be a bad idea to have onUpdate write an entry to device storage every e.g. 6hours with cur time and battery-percentage (i.e. as a temp code modification, just while one tries to measure effect of a new functionality on battery) ? or perhaps even println ?
i.e. then sideload to watch and examine after a day or two.