Uh oh!
There was an error while loading. Please reload this page.
Optimized vec::IntoIter::next_chunk impl - #98553
Conversation
rust-highfive
commented
Jun 26, 2022
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
rust-highfive
commented
Jun 26, 2022
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
bors
commented
Jun 29, 2022
☔ The latest upstream changes (presumably #98680) made this pull request unmergeable. Please resolve the merge conflicts. |
This comment was marked as duplicate.
This comment was marked as duplicate.
Uh oh!
There was an error while loading. Please reload this page.
Mark-Simulacrum
commented
Jul 26, 2022
r=me @bors rollup=never in case has unexpected perf effects |
``` test vec::bench_next_chunk ... bench: 696 ns/iter (+/- 22) x86_64v1, pr test vec::bench_next_chunk ... bench: 309 ns/iter (+/- 4) znver2, default test vec::bench_next_chunk ... bench: 17,272 ns/iter (+/- 117) znver2, pr test vec::bench_next_chunk ... bench: 211 ns/iter (+/- 3) ``` The znver2 default impl seems to be slow due to inlining decisions. It goes through `core::array::iter_next_chunk` which has a deeper call tree.
an adaption of the default impl's doctest
the8472
commented
Jul 26, 2022
@bors r=Mark-Simulacrum |
bors
commented
Jul 26, 2022
bors
commented
Jul 27, 2022
bors
commented
Jul 27, 2022
☀️ Test successful - checks-actions |
rust-timer
commented
Jul 27, 2022
Finished benchmarking commit (b573e10): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
On znver2 the default impl seems to be slow due to different inlining decisions. It goes through
core::array::iter_next_chunkwhich has a deep call tree.