-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Record query name when profiling "metadata_decode_entry" #75218
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
Conversation
r? @estebank (rust_highfive has picked a reviewer for you, use r? to override) |
cc @Mark-Simulacrum: It is possible to get this to show up on perf.rust-lang.org? |
I don't think so. We could just concat! the query name though (e.g., metadata_decode_item_attrs) |
0520c5e
to
c9bd943
Compare
@Mark-Simulacrum: I've updated the PR to use |
@bors try @rust-timer queue include=helloworld (Testing out new subset functionality; we shouldn't need a full build to test that this does what we expect) |
Awaiting bors try build completion |
⌛ Trying commit c9bd943 with merge 7534f1a4e75fd5e77b5db839bf19bb120e72935e... |
☀️ Try build successful - checks-actions, checks-azure |
Queued 7534f1a4e75fd5e77b5db839bf19bb120e72935e with parent 4b0882c, future comparison URL. |
Finished benchmarking try commit (7534f1a4e75fd5e77b5db839bf19bb120e72935e): comparison url. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up. @bors rollup=never |
Looks like it's working, see for example https://perf.rust-lang.org/detailed-query.html?sort_idx=-5&commit=7534f1a4e75fd5e77b5db839bf19bb120e72935e&benchmark=helloworld-opt&run_name=full I think this will indeed be useful to determine if regressions are coming from metadata loading or not -- right now it's hard to tell. We might even want to do some post-processing within perf to put these in a separate column, but I'm not sure about that. @bors r+ |
📌 Commit c9bd943 has been approved by |
☀️ Test successful - checks-actions, checks-azure |
No description provided.