-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
interpret: mark some hot functions inline(always) #130197
Conversation
Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri |
@bors try |
This comment has been minimized.
This comment has been minimized.
experiment: see where the perf regressions in rust-lang#129778 come from Let's see if we can figure out what caused the perf impact in rust-lang#129778. There are some extra functions in a few places so maybe more `inline(always)` helps... r? `@saethlin`
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (a775fd6): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking 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 Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)Results (secondary -2.6%)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.
CyclesResults (secondary -6.9%)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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 755.942s -> 756.905s (0.13%) |
That seems to be a good part of it, at least. |
recovers some of the perf regressions from rust-lang#129778
0852bf2
to
d104ded
Compare
I would really like to know why PGO+BOLT does the wrong thing here but the amount of perf on the table here isn't worth very much contributor time. @bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (5bce6d4): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)Results (secondary 6.0%)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.
CyclesResults (primary -5.2%)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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 758.053s -> 756.954s (-0.14%) |
That seems to recover a good part of the perf impact of #129778.
r? @saethlin