Uh oh!
There was an error while loading. Please reload this page.
Make DefIdrepr(C), optimize big-endian field order - #92012
Conversation
jackh726
commented
Dec 17, 2021
@bors try @rust-timer queue |
rust-timer
commented
Dec 17, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Dec 17, 2021
⌛ Trying commit 95a3e6adc5e724e93a62915b22380b6137be08db with merge 6de93a5f3c58289159da3d736b0361ca414bd34f... |
bors
commented
Dec 17, 2021
☀️ Try build successful - checks-actions |
rust-timer
commented
Dec 17, 2021
Queued 6de93a5f3c58289159da3d736b0361ca414bd34f with parent 5531927, future comparison URL. |
rust-timer
commented
Dec 17, 2021
Finished benchmarking commit (6de93a5f3c58289159da3d736b0361ca414bd34f): comparison url. Summary: This change led to very large relevant mixed results 🤷 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
llogiq
commented
Dec 17, 2021
That's weird. Even if I did something wrong, it shouldn't change the outcome by that much. |
michaelwoerister
commented
Dec 17, 2021
Yeah, that is weird. We'd expect the outcome to not change at all... |
jackh726
commented
Dec 17, 2021
I wonder if something is going wrong with perf: #91672 (comment) |
llogiq
commented
Dec 17, 2021
Yeah, that looks really fishy. Perhaps someone with access to perf can have a look? |
llogiq
commented
Dec 17, 2021
Ah it's likely because of rust-lang/rustc-perf#1123 |
Mark-Simulacrum
commented
Dec 17, 2021
@bors retry @rust-timer queue |
rust-timer
commented
Dec 17, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Dec 17, 2021
⌛ Trying commit 95a3e6adc5e724e93a62915b22380b6137be08db with merge 6a6e67427da0929979dc434855e205efe90bd2a3... |
bors
commented
Dec 18, 2021
☀️ Try build successful - checks-actions |
rust-timer
commented
Dec 18, 2021
Queued 6a6e67427da0929979dc434855e205efe90bd2a3 with parent 7abab1e, future comparison URL. |
rust-timer
commented
Dec 18, 2021
Finished benchmarking commit (6a6e67427da0929979dc434855e205efe90bd2a3): comparison url. Summary: This change led to moderate relevant regressions 😿 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never |
llogiq
commented
Dec 18, 2021
So there is something wrong. I'll have a look. |
Can we get another perf run? I wonder if removing the |
michaelwoerister
commented
Jan 3, 2022
perf.rlo seems to have problems with increased noise at the moment: rust-lang/rustc-perf#1126 Let's wait for that to be fixed and then revisit this. |
rust-timer
commented
Jan 3, 2022
Queued 586b3d2e1d80845457c6700c7e3deee19006521b with parent ddabe07, future comparison URL. |
rust-timer
commented
Jan 4, 2022
Finished benchmarking commit (586b3d2e1d80845457c6700c7e3deee19006521b): 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 |
llogiq
commented
Jan 4, 2022
Ok, that's what we were expecting. Now I'll add the |
Mark-Simulacrum
commented
Jan 4, 2022
@bors try @rust-timer queue |
rust-timer
commented
Jan 4, 2022
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Jan 4, 2022
⌛ Trying commit 7f7b551 with merge a5535ef48e9bb30104929abcdb9f1a6eec3d532f... |
bors
commented
Jan 4, 2022
☀️ Try build successful - checks-actions |
rust-timer
commented
Jan 4, 2022
Queued a5535ef48e9bb30104929abcdb9f1a6eec3d532f with parent 2b681ac, future comparison URL. |
rust-timer
commented
Jan 4, 2022
Finished benchmarking commit (a5535ef48e9bb30104929abcdb9f1a6eec3d532f): 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 |
llogiq
commented
Jan 4, 2022
Cool. This means we haven't lost any perf on any tier-1 systems and may have gained a little on big-endian 64-bit machines, not that there would be a lot of them around. |
michaelwoerister
commented
Jan 10, 2022
Looks good now! |
bors
commented
Jan 10, 2022
📌 Commit 7f7b551 has been approved by |
bors
commented
Jan 11, 2022
bors
commented
Jan 11, 2022
☀️ Test successful - checks-actions |
rust-timer
commented
Jan 11, 2022
Finished benchmarking commit (e4b1d58): 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. @rustbot label: -perf-regression |
r? @michaelwoerister