Repository navigation
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.
… r=<try> [DO NOT MERGE] search graph exploration
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (85ebe97): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @bors rollup=iffy rustc-perf 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 -0.0%, secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.0%, secondary 2.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 488.092s -> 487.544s (-0.11%) |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
… r=<try> [DO NOT MERGE] search graph exploration
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (e0c36dc): comparison URL. Overall result: ❌ regressions - please read:Benchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=iffy rustc-perf 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 1.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.3%, secondary -2.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 488.483s -> 488.641s (0.03%) |
b6d7db2 to
d53f593
Compare
|
@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.
… r=<try> [DO NOT MERGE] search graph exploration
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (b71d391): comparison URL. Overall result: no relevant changes - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary 0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 0.6%, secondary 1.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 490.291s -> 491.174s (0.18%) |
This comment has been minimized.
This comment has been minimized.
… r=<try> [DO NOT MERGE] search graph exploration
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (bc7feaa): comparison URL. Overall result: ❌ regressions - please read:Benchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=iffy rustc-perf 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 1.2%, secondary -2.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.7%, secondary -2.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 482.475s -> 481.881s (-0.12%) |
013c01e to
5fa7015
Compare
This comment has been minimized.
This comment has been minimized.
d7c2b87 to
a479bb0
Compare
|
@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.
… r=<try> [DO NOT MERGE] search graph exploration
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (73b8677): comparison URL. Overall result: no relevant changes - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary 2.2%, secondary 2.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 11.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 483.649s -> 483.96s (0.06%) |
a479bb0 to
08be60b
Compare
|
@bors try @rust-timer queue |
|
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
… r=<try> [DO NOT MERGE] search graph exploration
|
⌛ Trying commit 08be60b with merge f089070… To cancel the try build, run the command Workflow: https://github.com/rust-lang/rust/actions/runs/41862079576 |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💥 Test timed out after |
View all comments
I am trying a few things out in the search graph to see if any of them have an impact on performance. These are very small changes, mostly early returns or memoizing a few operations that we do quite a lot (though it might not be necessary). Just curious to see how it goes.
r? @ghost