Skip to content

Don't serialize empty predicates to metadata #89111

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

Conversation

Mark-Simulacrum
Copy link
Member

This keeps empty predicates out of the metadata. In practice, it seems like it
is quite common to have a default predicate set, so this should be a win.
Diesel, for example, has 40% of decoded predicates being default/empty.

I believe this is an attempt to implement this suggestion, and hopefully will help with that regression.

This keeps empty predicates out of the metadata. In practice, it seems like it
is quite common to have a default predicate set, so this should be a win.
@rust-highfive
Copy link
Contributor

r? @oli-obk

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 19, 2021
@Mark-Simulacrum
Copy link
Member Author

@bors try @rust-timer queue

@rust-timer
Copy link
Collaborator

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Sep 19, 2021
@bors
Copy link
Collaborator

bors commented Sep 19, 2021

⌛ Trying commit 7cb427e with merge 485510f732a05f117b3daa440af2d0413fff7cb4...

@bors
Copy link
Collaborator

bors commented Sep 19, 2021

☀️ Try build successful - checks-actions
Build commit: 485510f732a05f117b3daa440af2d0413fff7cb4 (485510f732a05f117b3daa440af2d0413fff7cb4)

@rust-timer
Copy link
Collaborator

Queued 485510f732a05f117b3daa440af2d0413fff7cb4 with parent 5ecc8ad, future comparison URL.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (485510f732a05f117b3daa440af2d0413fff7cb4): comparison url.

Summary: This change led to small relevant mixed results 🤷 in compiler performance.

  • Very small improvement in instruction counts (up to -0.3% on incr-full builds of ctfe-stress-4)
  • Small regression in instruction counts (up to 0.4% on full builds of coercions)

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 @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression

@rustbot rustbot added perf-regression Performance regression. and removed S-waiting-on-perf Status: Waiting on a perf run to be completed. labels Sep 20, 2021
@Mark-Simulacrum
Copy link
Member Author

Doesn't seem like this really has an effect. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perf-regression Performance regression. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants