-
Notifications
You must be signed in to change notification settings - Fork 13.4k
[perf] Fast path for coercions #142701
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] Fast path for coercions #142701
Conversation
@bors2 try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[perf] Fast path for coercions Check if the goal holds before trying to walk through the goal. If it certainly holds (or certainly does not), then don't select anything.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (840dfe0): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.7%, secondary -1.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -3.0%, secondary -1.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 692.944s -> 692.949s (0.00%) |
Ok so this is an improvement at least in the new trait solver, but only ~3%. I'll probably table this for now, because it also requires us to dramatically overhaul how we do diagnostics. |
Actually, what if we only check if the goal holds certainly... 🤔 |
41aaf68
to
b7d9e59
Compare
b7d9e59
to
92b2f28
Compare
@bors2 try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[perf] Fast path for coercions Check if the goal holds before trying to walk through the goal. If it certainly holds (or certainly does not), then don't select anything.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (f8500ef): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 1.6%, secondary -1.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 1.5%, secondary 4.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 691.904s -> 694.234s (0.34%) |
Check if the goal holds before trying to walk through the goal. If it certainly holds (or certainly does not), then don't select anything.