-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 experiment: disable large-move-check #132467
base: master
Are you sure you want to change the base?
Conversation
9ebeab8
to
c4d5c7e
Compare
@bors try |
This comment has been minimized.
This comment has been minimized.
perf experiment: disable large-move-check This is to figure out whether it's worth moving this check into a query, like we are doing for another mono-time check in rust-lang#132173.
Hm, this probably will show nothing since the move check is not enabled in the benchmarks. But I suspect for the case where the move check is enabled, moving it into a query can speed up incremental builds. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (ffdac0b): 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 the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (secondary -2.5%)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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 779.851s -> 779.759s (-0.01%) |
Wow, it's actually measurable in incremental builds. |
This is to figure out whether it's worth moving this check into a query, like we are doing for another mono-time check in #132173.