-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Rust: add some performance diagnostics #18116
base: main
Are you sure you want to change the base?
Conversation
This outputs some duration counts for various parts of the extraction process in the database in the form of telemetry diagnostics. The diagnostics format was preferred to putting things in the relational database as that will scale better to code scanning and is more flexible as for the data we can put into it without passing through the dbscheme. Also, although it's not the case yet, it will be possible to output diagnostics even if creation of the database fails.
/** | ||
* The string representation of this extractor step. | ||
*/ |
Check warning
Code scanning / CodeQL
Predicate QLDoc style. Warning
/** | ||
* The action this extractor step carried out. | ||
*/ |
Check warning
Code scanning / CodeQL
Predicate QLDoc style. Warning
/** | ||
* The file the extractor step was carried out on. | ||
*/ |
Check warning
Code scanning / CodeQL
Predicate QLDoc style. Warning
/** | ||
* The duration of the extractor step in milliseconds. | ||
*/ |
Check warning
Code scanning / CodeQL
Predicate QLDoc style. Warning
This outputs some duration counts for various parts of the extraction process in the database in the form of a per-file breakdown in the QL DB and a summary as telemetry diagnostics.
The QL DB entities do not use
codegen
because we currently can't include "extern" stuff (likeFile
in this case) into the generation machinery. This might be improved in the future.