This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Adjusting app workload to be close to the thermally sustainable threshold

(As per Pete's request I'm posting this as a new topic)

I have two questions:

1. Is there a recommended way to quickly benchmark the device on app startup and set various budgets / LOD tweaks accordingly, so that application is running as close to the thermally sustainable threshold?

2. Is there a recommended way to track energy usage / temperature so that the application can adapt in run-time to current conditions device is in and keep the workload sustainable yet optimal?

Also, any resource pointers / links relevant to above questions are more then welcome.

Thank you in advance,
Milan

Parents
  • Hi Milan, 

    Fast online benchmarking for thermal sustainability is challenging. A lot depends on the starting conditions; is the user standing in the sun, or inside in air conditioning, and that can change as the user moves around. The other issue is that thermal effects can change quite slowly. If a device is only marginally exceeding the thermal dissipation rate for the device it may heat up over a period of tens of minutes, not the few tens of seconds you need for a load-time test.  

    What's really needed is some kind of live feedback so you can adjust in real time, and unfortunately there is no standard Android API for this at the moment. Some (but not many) Android devices expose thermal sensors via the Linux hwmon infrastructure. There are also some vendor-specific solutions such as this one: 

    As you might expect this is a "hot topic", if you forgive the phrasing, so we are actively working with our ecosystem partners to come up with a more widely available solution here. 

    Kind regards, 
    Pete 

Reply
  • Hi Milan, 

    Fast online benchmarking for thermal sustainability is challenging. A lot depends on the starting conditions; is the user standing in the sun, or inside in air conditioning, and that can change as the user moves around. The other issue is that thermal effects can change quite slowly. If a device is only marginally exceeding the thermal dissipation rate for the device it may heat up over a period of tens of minutes, not the few tens of seconds you need for a load-time test.  

    What's really needed is some kind of live feedback so you can adjust in real time, and unfortunately there is no standard Android API for this at the moment. Some (but not many) Android devices expose thermal sensors via the Linux hwmon infrastructure. There are also some vendor-specific solutions such as this one: 

    As you might expect this is a "hot topic", if you forgive the phrasing, so we are actively working with our ecosystem partners to come up with a more widely available solution here. 

    Kind regards, 
    Pete 

Children