Would like D scripts for tracing transactions in Nexus #7224
Labels
Debugging
For when you want better data in debugging an issue (log messages, post mortem debugging, and more)
Comments
bnaecker
added
the
Debugging
bnaecker
added a commit
that referenced
this issue
Dec 12, 2024
- Adds a script for tracing all transactions run by Nexus, including their overall latency and the number of statements in each one. - Move all existing scripts to a Nexus subdirectory, and then include that whole directory in the Omicron zone for Nexus itself. - Closes #7224
bnaecker
added a commit
that referenced
this issue
Dec 13, 2024
- Adds a script for tracing all transactions run by Nexus, including their overall latency and the number of statements in each one. - Move all existing scripts to a Nexus subdirectory, and then include that whole directory in the Omicron zone for Nexus itself. - Closes #7224
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've recently run into some issues around large transactions causing performance degradation. We have some D scripts for tracing queries, such as all queries, or the slowest ones every 5 seconds. We've also added some better probes around transactions specifically, which merged in #7219. With that, we can now implement some D scripts to trace those transactions specifically, such as their overall latency, or the number of queries run in them, etc.
We should add those scripts, and also deploy those scripts in the Nexus zones we build via
omicron-package.The text was updated successfully, but these errors were encountered: