-
Notifications
You must be signed in to change notification settings - Fork 660
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
feat: improve visibility for runtime performance #4038
Conversation
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.
Will info_span
print the log on the INFO level? That is probably not what we want
This PR has been automatically marked as stale because it has not had recent activity in the 2 weeks. |
@matklad please resolve the merge conflict and fix CI :) |
tracing::span records how long it took to run a block of code and prints this into into log. See https://github.com/near/nearcore/blob/ff01c544ce2675fadbf0284af52b356a383b27a8/docs/architecture.md#runtimenear-vm-runner for the info on the tracing infra
Rebased, applying auto merge as I don't think anything changed here. cc @near/nodex (@bowenwang1996, should we create this team alias for GH pings?), I think we might want more of this throughout the stack! |
The issue for "have more of this" is #4040 |
tracing::span records how long it took to run a block of code and prints
this into into log.
See
https://github.com/near/nearcore/blob/ff01c544ce2675fadbf0284af52b356a383b27a8/docs/architecture.md#runtimenear-vm-runner
for the info on the tracing infra
Test Plan
Only active with debug logging level enabled, doesn't need additional testing.