Skip to content

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

Merged
merged 1 commit into from
Aug 6, 2020

Conversation

Aaron1011
Copy link
Member

No description provided.

@rust-highfive
Copy link
Contributor

r? @estebank

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 6, 2020
@Aaron1011
Copy link
Member Author

cc @Mark-Simulacrum: It is possible to get this to show up on perf.rust-lang.org?

@Mark-Simulacrum
Copy link
Member

I don't think so. We could just concat! the query name though (e.g., metadata_decode_item_attrs)

@Aaron1011 Aaron1011 force-pushed the feature/prof-metadata-query branch from 0520c5e to c9bd943 Compare August 6, 2020 13:33
@Aaron1011
Copy link
Member Author

@Mark-Simulacrum: I've updated the PR to use concat!

@Mark-Simulacrum
Copy link
Member

@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)

@rust-timer
Copy link
Collaborator

Awaiting bors try build completion

@bors
Copy link
Collaborator

bors commented Aug 6, 2020

⌛ Trying commit c9bd943 with merge 7534f1a4e75fd5e77b5db839bf19bb120e72935e...

@bors
Copy link
Collaborator

bors commented Aug 6, 2020

☀️ Try build successful - checks-actions, checks-azure
Build commit: 7534f1a4e75fd5e77b5db839bf19bb120e72935e (7534f1a4e75fd5e77b5db839bf19bb120e72935e)

@rust-timer
Copy link
Collaborator

Queued 7534f1a4e75fd5e77b5db839bf19bb120e72935e with parent 4b0882c, future comparison URL.

@rust-timer
Copy link
Collaborator

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 rollup- to bors.

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

@Mark-Simulacrum
Copy link
Member

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+

@bors
Copy link
Collaborator

bors commented Aug 6, 2020

📌 Commit c9bd943 has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 6, 2020
@bors
Copy link
Collaborator

bors commented Aug 6, 2020

⌛ Testing commit c9bd943 with merge 0d75c91...

@bors
Copy link
Collaborator

bors commented Aug 6, 2020

☀️ Test successful - checks-actions, checks-azure
Approved by: Mark-Simulacrum
Pushing 0d75c91 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Aug 6, 2020
@bors bors merged commit 0d75c91 into rust-lang:master Aug 6, 2020
@cuviper cuviper added this to the 1.47.0 milestone May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants