-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Try to cache region_scope_tree as a query #97383
Try to cache region_scope_tree as a query #97383
Conversation
Some changes occurred in src/tools/clippy. cc @rust-lang/clippy |
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Insufficient permissions to issue commands to rust-timer. |
@dingxiangfei2009: 🔑 Insufficient privileges: not in try users |
😢 Okay. May I request for a test run with |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 4c6074f with merge 209f91e1787d0d29a0e566fa93f35d52e60ea84a... |
☀️ Try build successful - checks-actions |
Queued 209f91e1787d0d29a0e566fa93f35d52e60ea84a with parent 6ac8ada, future comparison URL. |
r? rust-lang/compiler |
Finished benchmarking commit (209f91e1787d0d29a0e566fa93f35d52e60ea84a): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
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 |
I dug into this with @dingxiangfei2009 -- this PR seems like a good next step. I hadn't anticipated constructing the region-scope-tree to be a significant cost, but it makes sense, particularly in incremental builds, where we are doing less work overall, and so it pays to avoid it. I think we could probably optimize things further by removing the |
r=me with that change |
@bors delegate+ |
✌️ @dingxiangfei2009 can now approve this pull request |
This comment has been minimized.
This comment has been minimized.
⌛ Testing commit 5ced891 with merge 35463d158c63c4b4585f5038c3659fa1eca061bd... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit 5ced891 with merge f65e03b283bd1d4f2c8c9280635280236aad50cf... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Rémy Rakic <remy.rakic+github@gmail.com>
@bors r+ |
📌 Commit cd76f2e has been approved by |
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (4f39fb1): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
This PR will attempt to restore
region_scope_tree
as a query so that caching works again. It seems thatregion_scope_tree
could be re-computed for nested items after all, which could explain the performance regression introduced by #95563.cc @Mark-Simulacrum @pnkfelix I will try to trigger a perf run here.