-
Notifications
You must be signed in to change notification settings - Fork 81
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
Tvm explorer infrastructure #92
Conversation
- Enchance the span filling - Enchance the schedule visualization
- Rebased
9058a33
to
27e7cfb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing all this work the improve debugging in TVM! I think this is a great step forward.
# Drawbacks | ||
[drawbacks]: #drawbacks | ||
|
||
* Process extra debug information would cause longer compilation time: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you done any tests to see how much this may increase compile times? My guess is it would not be too bad.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tkonolige,
Thanks for comments! :D
Yes, we have a profiling results in the forum.
For your reference. You can find the details in the end of this post.
https://discuss.tvm.apache.org/t/pre-rfc-tvm-explorer-infrastructure/13457/14?u=chunit
i think we are good on the pre-RFC thread, let's merge this then. @chunit-quic can you create an RFC tracking issue (i.e. "feature tracking" here) for this one? |
Hi @areusch , |
Hi community:
Follow the guide in the README.md, this PR is summited for the forum topic:
https://discuss.tvm.apache.org/t/tvm-explorer-infrastructure/13457
Thank you!