... | ... | @@ -21,16 +21,16 @@ More specifically, each selection functionality is described below: |
|
|
|
|
|
The following image shows the static Consumption Analysis panel which is a part of the Energy toolbox front-end:
|
|
|
|
|
|
![image](https://gitlab.seis.iti.gr/sdk4ed-wiki/wiki-home/wikis/uploads/energy_static.png)
|
|
|
![energy_static](uploads/aec776ddc13f897ffc403df5a8a97075/energy_static.png)
|
|
|
|
|
|
This panel consists of two parts:
|
|
|
- Profiling results per function or loop: The energy estimation can be reported at function-level and at loop-level. Developers can configure this selecting by “Granularity”. The energy estimation values for each row in the table are adjusted based on the selected granularity level.
|
|
|
|
|
|
![image](https://gitlab.seis.iti.gr/sdk4ed-wiki/wiki-home/wikis/uploads/energy_select_granularity.png)
|
|
|
![energy_select_granularity](uploads/0b0756024e463eaf309b437f3fe709c1/energy_select_granularity.PNG)
|
|
|
|
|
|
- Estimating the energy consumption across whole application for different embedded platforms: There is a drop-down list of the available devices that are already imported in the Energy Toolbox:
|
|
|
|
|
|
![image](https://gitlab.seis.iti.gr/sdk4ed-wiki/wiki-home/wikis/uploads/energy_select_platform.png)
|
|
|
![energy_select_platform](uploads/1716ad3de30683c3bd303144480cdf15/energy_select_platform.PNG)
|
|
|
|
|
|
In addition, there is a form where the user can set the number of iterations per loop. In the left box the loop id is selected, while in the right box the number of iterations is set. After pressing the “Calculate” button all the energy estimations are re-calculated and the user can proceed in setting the iterations number for another loop.
|
|
|
|
... | ... | @@ -64,6 +64,6 @@ The proposed optimizations per hotspot are depicted in the lowest part of the en |
|
|
|
|
|
The Energy Toolbox also provides the opportunity to present the static analysis estimations for all the project commits that have been analysed using the Toolbox in the past, retrieving the information from the embedded database. An example of the history analysis results is presented in the next picture:
|
|
|
|
|
|
![image](https://gitlab.seis.iti.gr/sdk4ed-wiki/wiki-home/wikis/uploads/energy_history.png)
|
|
|
![energy_history](uploads/92a8866c6fafdd16486896ad7e233fe1/energy_history.PNG)
|
|
|
|
|
|
Based on these results, a user could find the estimated energy consumption and execution time for each version of the project under analysis for the use of different platforms. In the presented example the energy is lower for the use of ARM Cortex M0+, while the estimated execution time is higher compared to the execution of the application in the more complex ARM Cortex A-57. There is also an increase in Energy Consumption (about in the middle of the project’s history). A new functionality might be added in these commits, which does not exist after certain versions of the project. |
|
|
\ No newline at end of file |