-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
main: add flag to write execution traces #2223
base: master
Are you sure you want to change the base?
main: add flag to write execution traces #2223
Conversation
Execution traces are part of the go runtime tooling and is useful to check what is slowing down the ibd. For example, a slow ibd because of slow block downloads from peers won't show up on cpu profiling but will on a trace.
Pull Request Test Coverage Report for Build 10261087623Details
💛 - Coveralls |
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.
tACK, LGTM 🎉
@@ -114,6 +114,7 @@ type config struct { | |||
ConnectPeers []string `long:"connect" description:"Connect only to the specified peers at startup"` | |||
CPUProfile string `long:"cpuprofile" description:"Write CPU profile to the specified file"` | |||
MemoryProfile string `long:"memprofile" description:"Write memory profile to the specified file"` | |||
TraceProfile string `long:"trace" description:"Write execution trace to the specified file"` |
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.
nit: call the flag traceprofile
to not confuse it with a log level and be more in line with the other profile flags?
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.
Makes sense ^
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.
Bump on this, can get merged once addressed.
Execution traces are part of the go runtime tooling and is useful to check what is slowing down the ibd. For example, a slow ibd because of slow block downloads from peers won't show up on cpu profiling but will on a trace.
Also execution tracing has gotten a lot better with go 1.22