-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Remove ArenaCacheSelector for visible_parent_map query #92168
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
Please, kindly schedule a perf run, in accordinness with #87349 (comment) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit c44eee3 with merge 0c93ad62f49d9243ff8ffe7841f87266d31fd1ff... |
☀️ Try build successful - checks-actions |
Queued 0c93ad62f49d9243ff8ffe7841f87266d31fd1ff with parent 8ad3c1d, future comparison URL. |
Finished benchmarking commit (0c93ad62f49d9243ff8ffe7841f87266d31fd1ff): comparison url. Summary: This change led to moderate relevant improvements 🎉 in compiler performance.
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 led to changes in compiler perf. @bors rollup=never |
Surprising results, that DefIdMap cloning has lower performance cost, than Lrc wrapper. What do you think @Mark-Simulacrum ? |
@bors try @rust-timer queue I think this might've been some amount of noise when it was run, so let's re-check just in case. |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit c44eee3 with merge fa5f57f91c3963cd17ff478dd1f40cc7b2e14f98... |
☀️ Try build successful - checks-actions |
Queued fa5f57f91c3963cd17ff478dd1f40cc7b2e14f98 with parent 5883b87, future comparison URL. |
Finished benchmarking commit (fa5f57f91c3963cd17ff478dd1f40cc7b2e14f98): comparison url. Summary: This benchmark run did not return any relevant changes. 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 led to changes in compiler perf. @bors rollup=never |
Closing in favor of #92169. |
No description provided.