Uh oh!
There was an error while loading. Please reload this page.
[rustdoc] Cleanup "highlight::end_expansion" - #147237
Conversation
yotamofek
commented
Oct 1, 2025
This basically just removes two |
GuillaumeGomez
commented
Oct 1, 2025
I'm curious to see the impact too. @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…xpansion, r=<try> [rustdoc] Optimize "highlight::end_expansion"
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Oct 1, 2025
Finished benchmarking commit (ce6801f): comparison URL. Overall result: ❌ regressions - no action neededBenchmarking 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. @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 -2.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
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: 470.999s -> 472.425s (0.30%) |
yotamofek
commented
Oct 1, 2025
Regression is on "opt" profile test, so most likely just noise. Otherwise perf is neutral :( |
GuillaumeGomez
commented
Oct 2, 2025
Go ahead then, we can run another perf check once you pushed the change. |
fd23589 to
78c2e58Compareyotamofek
commented
Oct 2, 2025
Done. |
GuillaumeGomez
commented
Oct 2, 2025
Round 2! @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.
…xpansion, r=<try> [rustdoc] Optimize "highlight::end_expansion"
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Oct 2, 2025
Finished benchmarking commit (67e3f35): comparison URL. Overall result: no relevant changes - no action neededBenchmarking 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. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary -0.3%, secondary 2.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.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: 470.352s -> 470.242s (-0.02%) |
yotamofek
commented
Oct 6, 2025
@GuillaumeGomez perf is neutral, WDYT about merging this in? :) |
GuillaumeGomez
commented
Oct 6, 2025
Code is simpler so definitely! @bors r+ rollup |
bors
commented
Oct 6, 2025
Uh oh!
There was an error while loading. Please reload this page.
Rollup merge of #147237 - yotamofek:pr/rustdoc/highlight/optimize-end_expansion, r=GuillaumeGomez [rustdoc] Cleanup "highlight::end_expansion" ~Looks like a ~5% improvement on the highlight benchmark. Obviously, highlighting is only a small part of rustdoc's runtime, so improvement won't be as large on rustc-perf (if there's even an improvement), but holding fingers for a nice gain.~ Perf seems neutral, but IMHO this is a nice small cleanup regardless. r? `@GuillaumeGomez` (& perf run please!)
Rollup of 3 pull requests Successful merges: - rust-lang/rust#146027 (support link modifier `as-needed` for raw-dylib-elf) - rust-lang/rust#146874 (compiler: Hint at multiple crate versions if trait impl is for wrong ADT ) - rust-lang/rust#147237 ([rustdoc] Cleanup "highlight::end_expansion") r? `@ghost` `@rustbot` modify labels: rollup
~Looks like a
5% improvement on the highlight benchmark.Obviously, highlighting is only a small part of rustdoc's runtime, so improvement won't be as large on rustc-perf (if there's even an improvement), but holding fingers for a nice gain.
Perf seems neutral, but IMHO this is a nice small cleanup regardless.
r? @GuillaumeGomez (& perf run please!)