-
Notifications
You must be signed in to change notification settings - Fork 106
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
chore: Add tracing for debuging the js procedure slowness #1552
Conversation
This will be extremely useful during our switch from docker to JS |
backend/src/procedure/mod.rs
Outdated
tracing::trace!( | ||
"Procedure execute {} {} - {:?}", | ||
match self { | ||
PackageProcedure::Docker(_) => "docker", | ||
PackageProcedure::Script(_) => "JS", | ||
}, | ||
pkg_id, | ||
name | ||
); |
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.
yeesh this is a lot of visual space for a trace log. Is there any way to make it more innocuous?
I may encourage display instances for Package Procedure
and then you can eliminate the case statement and probably smash this to a single line.
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 the idea. It did reduce the vertical garbage
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.
Make display instance for package procedure. If Display would be wrong, write a custom function for rendering. This should make the match statement go away here and reduce visual clutter to a single line, which is appropriate for a trace log.
While debuging why configSet was slow, was using this trace. @chrisguida thought it would be nice if others could trace this too.