-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
Use repeat_packed when calculating layouts in RawVec
#151389
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
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Use `repeat_packed` when calculating layouts in `RawVec`
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (7b0717a): 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 (secondary -3.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 3.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.0%, secondary -0.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 473.058s -> 476.789s (0.79%) |
|
Yup, looks like overall that's enough to undo the regression from #148769 (comment) -- for example, that was 12 red in doc, this is 19 green in doc. (That said, I see no reason that doc icounts should have been so impacted by this, that seems weird, and there's probably something that someone could investigate about it, but I won't be.) |
|
Great! |
This comment has been minimized.
This comment has been minimized.
Use `repeat_packed` when calculating layouts in `RawVec` Seeing whether this helps the icounts seen in #148769 (comment)
This comment has been minimized.
This comment has been minimized.
|
💔 Test for f8f606f failed: CI. Failed job:
|
This comment has been minimized.
This comment has been minimized.
Use `repeat_packed` when calculating layouts in `RawVec` Seeing whether this helps the icounts seen in #148769 (comment)
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for 551d78c failed: CI. Failed job:
|
|
@bors retry |
This comment has been minimized.
This comment has been minimized.
Use `repeat_packed` when calculating layouts in `RawVec` Seeing whether this helps the icounts seen in #148769 (comment)
|
💔 Test for 9b1aba6 failed: CI. Failed job:
|
|
@bors retry (dist-x86_64-msvc looks like it just disappeared? No raw logs.) |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 1655912 (parent) -> 9283d59 (this PR) Test differencesShow 3 test diffs3 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 9283d592deb2887311b9fa95027fd78c2172e554 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (9283d59): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression 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 2.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -5.4%, secondary 0.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.2%, secondary -0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 472.43s -> 471.36s (-0.23%) |
|
Results match pre-merge run. Net positive, addresses previous regression, see #151389 (comment) @rustbot label: +perf-regression-triaged |
Seeing whether this helps the icounts seen in #148769 (comment)