-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add memory_report.py to generate a FLASH/RAM report #37525
base: master
Are you sure you want to change the base?
Conversation
This PR adds a python script to analyze built targets and generate an HTML (or CSV) report of FLASH/RAM usage for each example app.
Changed Files
|
PR #37525: Size comparison from 9c8cb33 to 02bd84c Full report (3 builds for cc32xx, stm32)
|
PR #37525: Size comparison from 9c8cb33 to d4bcec7 Full report (72 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
The current HTML displays a snapshot of the FLASH and RAM usage for Linux example applications. To track usage trends over time, we need to collect and store daily FLASH and RAM data in a database (CSV). This data will then be used to generate a static HTML page that visualizes the daily FLASH consumption trends, similar to Time Series Charts in Looker Studio. |
Agreed, this PR is step 1, it scans all of the targets build in the OUT directory and collects flash and ram usage into a CSV file for a single day. I'm still not sure we should save multiple CSV files in disk. As I mentioned before, we are tinkering with the VM all the time and there's a high change this data will be wiped when we upgrade the VM or delete the disk for some reason. |
PR #37525: Size comparison from 33ca47e to 0144546 Full report (72 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
This PR adds a python script to analyze built targets and generate an HTML (or CSV) report of FLASH/RAM usage for each example app.
For now, this will run daily and provide and provide a snapshot or the FLASH/RAM usage in a table, similar to what has been done for conformance in (https://matter-build-automation.ue.r.appspot.com/conformance_report.html).
In the future, we plan to aggregate this data into a database and provide a better way to visualize historical data.
Testing
Tested it generates an HTML page locally. See screenshot below: