Try to fix perf regression in rustdoc after hir attributes#134376
Try to fix perf regression in rustdoc after hir attributes#134376bors merged 1 commit intorust-lang:masterfrom
Conversation
|
@rustbot label +A-attributes +T-rustdoc |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Try to fix perf regression in rustdoc after hir attributes Slight performance regression introduced in rust-lang#131808 r? `@jieyouxu`
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (595c57d): 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 (primary -0.7%, secondary -3.7%)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 -1.5%, secondary -1.3%)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: 773.825s -> 770.612s (-0.42%) |
|
Looks good. Thanks! @bors r+ rollup |
|
@bors rollup=never (perf) |
|
Does it? I still wanted to revisit this cause it doesn't actually solve the problem completely. It's a small improvement but there's still something wrong |
|
More improvements are always welcome, but this does in fact seem to fully resolve the original perf. regression. Good job :) |
…youxu Try to fix perf regression in rustdoc after hir attributes Slight performance regression introduced in rust-lang#131808 r? `@jieyouxu`
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test failed - checks-actions |
|
@bors retry (msvc skull_emoji.jpg) |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (7e6bf00): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression 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.
CyclesResults (primary -1.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: 769.242s -> 769.759s (0.07%) |
Slight performance regression introduced in #131808
r? @jieyouxu