-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Perf-Testing: Cleanups for perf regression caused by initial implementation of RFC 3191 #96795
Conversation
r? @jackh726 (rust-highfive has picked a reviewer for you, use r? to override) |
r? @wesleywiser |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit da7556400d03631b132ba06450724220ebb8f745 with merge c82d40f772049273ff47b19f47a22915e324459f... |
☀️ Try build successful - checks-actions |
Queued c82d40f772049273ff47b19f47a22915e324459f with parent 4799baa, future comparison URL. |
Finished benchmarking commit (c82d40f772049273ff47b19f47a22915e324459f): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never |
da75564
to
9f9c6f0
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 5797c9158ae0f27c3f1f8af1b91fb192687b039f with merge f255f5f55d944ee5b4eb745966edac0924631545... |
☀️ Try build successful - checks-actions |
Queued f255f5f55d944ee5b4eb745966edac0924631545 with parent 08b4f1b, future comparison URL. |
Finished benchmarking commit (f255f5f55d944ee5b4eb745966edac0924631545): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never |
Queued 5e04e4593df4d3137047ada6ef58386fa6facb4a with parent f1f721e, future comparison URL. |
Finished benchmarking commit (5e04e4593df4d3137047ada6ef58386fa6facb4a): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never |
…in_macros` to `rustc_expand`.
…o test the overhead caused by adding new symbols.
df65db3
to
3c87c4d
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 3c87c4d with merge 56c049b2e9a3a9185825ecfeeec6dbddee17bc66... |
☀️ Try build successful - checks-actions |
Queued 56c049b2e9a3a9185825ecfeeec6dbddee17bc66 with parent c52b9c1, future comparison URL. |
Finished benchmarking commit (56c049b2e9a3a9185825ecfeeec6dbddee17bc66): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 485e105 with merge 1aa8aeb6901dae58833b658df1c0aae2384fc792... |
☀️ Try build successful - checks-actions |
Queued 1aa8aeb6901dae58833b658df1c0aae2384fc792 with parent 4c5f6e6, future comparison URL. |
Finished benchmarking commit (1aa8aeb6901dae58833b658df1c0aae2384fc792): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
The tracking issue for that this PR was tracking has been closed after posting results of these experiments. |
This is currently a Draft and not ready for review.
PR #91779 implemented initial support for RFC 3191 which caused a noticeable perf regression tracked by #96786. Implementing a few different changes to drive down the perf regression such as only querying for the
#[debugger_visualizer]
attribute when targeting msvc.