Skip to content
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

[Tracking Issue] Estimate memory footprint in microTVM #10142

Closed
areusch opened this issue Feb 2, 2022 · 0 comments
Closed

[Tracking Issue] Estimate memory footprint in microTVM #10142

areusch opened this issue Feb 2, 2022 · 0 comments
Labels
type:rfc-tracking RFC progress tracking. Ref: https://github.com/apache/tvm-rfcs vert:micro MicroTVM: src/runtime/micro, src/runtime/crt, apps/microtvm

Comments

@areusch
Copy link
Contributor

areusch commented Feb 2, 2022

microTVM currently reports some memory usage numbers, but a true estimate of the RAM footprint needs to be made by examining the output of the Unified Static Memory Planner being implemented in #8404. This issue is an explicit tracking issue to cover the work needed to generate this estimate and add it to Model Library Format.

@areusch areusch added the type:rfc-tracking RFC progress tracking. Ref: https://github.com/apache/tvm-rfcs label Feb 2, 2022
@areusch areusch added the needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it label Oct 19, 2022
@driazati driazati added vert:micro MicroTVM: src/runtime/micro, src/runtime/crt, apps/microtvm and removed needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it labels Oct 19, 2022
@tqchen tqchen closed this as completed Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:rfc-tracking RFC progress tracking. Ref: https://github.com/apache/tvm-rfcs vert:micro MicroTVM: src/runtime/micro, src/runtime/crt, apps/microtvm
Projects
None yet
Development

No branches or pull requests

3 participants