Uh oh!
There was an error while loading. Please reload this page.
rustc_metadata: Merge items from extern blocks into their parent modules during metadata encoding rather than during metadata decoding - #92153
Conversation
rust-highfive
commented
Dec 21, 2021
(rust-highfive has picked a reviewer for you, use r? to override) |
petrochenkov
commented
Dec 21, 2021
@bors try @rust-timer queue |
rust-timer
commented
Dec 21, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Dec 21, 2021
⌛ Trying commit f6052e3c3952ef9fb66aade565e0e0f92374dcd7 with merge b821a59989a52a2fdf83c4c28319ed44b7ea78c1... |
bors
commented
Dec 21, 2021
☀️ Try build successful - checks-actions |
rust-timer
commented
Dec 21, 2021
Queued b821a59989a52a2fdf83c4c28319ed44b7ea78c1 with parent 46171fa, future comparison URL. |
rust-timer
commented
Dec 21, 2021
Finished benchmarking commit (b821a59989a52a2fdf83c4c28319ed44b7ea78c1): comparison url. Summary: This change led to large 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 |
petrochenkov
commented
Dec 21, 2021
We are doing less (in the worst case no more) work during both encoding and decoding, but apparently the My plan was to simplify |
Mark-Simulacrum
commented
Dec 21, 2021
It may be worth re-running now that rust-lang/rustc-perf#1126 has at least partially been patched. |
f6052e3 to
6100620Comparepetrochenkov
commented
Dec 22, 2021
Yeah, given that results in e.g. #92156 don't make any sense I can only assume that it's all noise. @bors try @rust-timer queue |
rust-timer
commented
Dec 22, 2021
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
bors
commented
Dec 22, 2021
⌛ Trying commit 6100620fe97a0b4274034d83bd1f06e6e730153f with merge 0fb8c713229632bcd6bf7499ab7cf3de179d1d54... |
bors
commented
Dec 22, 2021
☀️ Try build successful - checks-actions |
rust-timer
commented
Dec 22, 2021
Queued 0fb8c713229632bcd6bf7499ab7cf3de179d1d54 with parent e100ec5, future comparison URL. |
rust-timer
commented
Dec 22, 2021
Finished benchmarking commit (0fb8c713229632bcd6bf7499ab7cf3de179d1d54): comparison url. Summary: This change led to large 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 |
petrochenkov
commented
Dec 28, 2021
r? @cjgillot |
cjgillot
commented
Dec 28, 2021
@bors r+ |
bors
commented
Dec 28, 2021
📌 Commit a5efcea has been approved by |
bors
commented
Dec 28, 2021
⌛ Testing commit a5efcea with merge 27bbaf5f378ca48047a53312d8aded2e2d985755... |
bors
commented
Dec 28, 2021
💔 Test failed - checks-actions |
rust-log-analyzer
commented
Dec 28, 2021
The job Click to see the possible cause of the failure (guessed by this bot) |
matthiaskrgr
commented
Dec 28, 2021
bors
commented
Dec 28, 2021
bors
commented
Dec 28, 2021
☀️ Test successful - checks-actions |
rust-timer
commented
Dec 28, 2021
Finished benchmarking commit (442248d): comparison url. Summary: This change led to small relevant regressions 😿 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression |
petrochenkov
commented
Dec 29, 2021
The results don't make any sense to me. |
pnkfelix
commented
Jan 4, 2022
This appears to be an improvement to the overall pipeline for compilation (assuming that in the common case overall, metadata is decoded far more often than encoded), and thus even if this small regression is real (which I'm not certain it is, especially given that all the data points are annotated with "?" in the perf output), I think we would accept the regression anyway. @rustbot label: +perf-regression-triaged |
No description provided.