Skip to content
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

[perf] delete no-op caching optimization from (old) trait solver #107798

Conversation

lukas-code
Copy link
Contributor

This code path is only taken if the caller bounds are already empty. Found in #107688 (comment).

r? ghost

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 8, 2023
@the8472
Copy link
Member

the8472 commented Feb 8, 2023

@bors try @rust-timer queue

@rust-timer

This comment has been minimized.

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Feb 8, 2023
@bors
Copy link
Contributor

bors commented Feb 8, 2023

⌛ Trying commit 5c6deaf with merge 3f8bf38ccb0c12ffdfc99edf4db18cea885fc33a...

@bors
Copy link
Contributor

bors commented Feb 8, 2023

☀️ Try build successful - checks-actions
Build commit: 3f8bf38ccb0c12ffdfc99edf4db18cea885fc33a (3f8bf38ccb0c12ffdfc99edf4db18cea885fc33a)

1 similar comment
@bors
Copy link
Contributor

bors commented Feb 8, 2023

☀️ Try build successful - checks-actions
Build commit: 3f8bf38ccb0c12ffdfc99edf4db18cea885fc33a (3f8bf38ccb0c12ffdfc99edf4db18cea885fc33a)

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (3f8bf38ccb0c12ffdfc99edf4db18cea885fc33a): comparison URL.

Overall result: ✅ improvements - no action needed

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
@rustbot label: -S-waiting-on-perf -perf-regression

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-1.3% [-1.5%, -1.2%] 2
Improvements ✅
(secondary)
-3.6% [-4.2%, -3.2%] 6
All ❌✅ (primary) -1.3% [-1.5%, -1.2%] 2

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-3.2% [-3.3%, -3.1%] 2
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -3.2% [-3.3%, -3.1%] 2

Cycles

This benchmark run did not return any relevant results for this metric.

@rustbot rustbot removed the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Feb 8, 2023
@lqd
Copy link
Member

lqd commented Feb 8, 2023

Note that cranelift-codegen and keccak are currently noisy and should (hopefully) stabilize soon, so that a new future perf run has more trustworthy results (or do a rustc-perf run locally to see if they're similar).

image

@lukas-code
Copy link
Contributor Author

Yeah all improvements here are just the inverse of #107778 (comment), so I'm no convinced that this is worth it.

@lukas-code lukas-code closed this Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants