-
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
Refactorings in preparation for #70951 #80452
Conversation
This comment has been minimized.
This comment has been minimized.
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 18680f79638ca301cfd519e9fc95ded7f74288a1 with merge d60872e6f17fb2b7d675e0e4556cf62116d6fa96... |
☀️ Try build successful - checks-actions |
Queued d60872e6f17fb2b7d675e0e4556cf62116d6fa96 with parent 2987785, future comparison URL. @rustbot label: +S-waiting-on-perf |
Finished benchmarking try commit (d60872e6f17fb2b7d675e0e4556cf62116d6fa96): 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 |
Ok, so at least we know it's not related to moving it across crates, but just due to the dynamic dispatch (or most likely, due to the lack of inlining) |
28f255e
to
37065a1
Compare
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit 37065a1020ad6ba1b7d41dca496e351be0b0730d with merge de2a8b56260fa483d30f8c31c85624a493e62b04... |
☀️ Try build successful - checks-actions |
Queued de2a8b56260fa483d30f8c31c85624a493e62b04 with parent 61f5a00, future comparison URL. @rustbot label: +S-waiting-on-perf |
Finished benchmarking try commit (de2a8b56260fa483d30f8c31c85624a493e62b04): 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 |
Big regressions of up to 7%. |
@bors try @rust-timer queue |
Awaiting bors try build completion. |
⌛ Trying commit fed215e43224e73c5fabb2562d8537076c7ab458 with merge 5b9b411f66cbd861eb57e9cc971f3f941acb7151... |
☀️ Try build successful - checks-actions |
The per-Key choice was not used.
0a05868
to
b0927af
Compare
Now that #81855 has been merged, and its perf has been validated: |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit b0927af with merge cfcfe8cab11f3081dc476759aec8d9e794b4afd7... |
☀️ Try build successful - checks-actions |
Queued cfcfe8cab11f3081dc476759aec8d9e794b4afd7 with parent d1462d8, future comparison URL. |
Finished benchmarking try commit (cfcfe8cab11f3081dc476759aec8d9e794b4afd7): 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 |
Split out of #70951 to investigate perf.
r? @oli-obk