dotnet / perf-autofiling-issues

A landing place for auto-filed performance issues before they receive triage
MIT License
9 stars 4 forks source link

[Perf] Linux/arm64: 1 Improvement on 8/11/2024 3:44:20 AM #39886

Open performanceautofiler[bot] opened 2 months ago

performanceautofiler[bot] commented 2 months ago

Run Information

Name Value
Architecture arm64
OS ubuntu 22.04
Queue AmpereUbuntu
Baseline 5b921e2f3dc0c8654482525f93b9c7d261437077
Compare d3cd5b6510871b97056ed421ae84be4805f547e6
Diff Diff
Configs CompilationMode:tiered, RunKind:micro

Improvements in BenchmarksGame.FannkuchRedux_5

Benchmark Baseline Test Test/Base Test Quality Edge Detector Baseline IR Compare IR IR Ratio
62.76 ms 29.82 ms 0.48 0.09 False

graph Test Report

Repro

General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md

git clone https://github.com/dotnet/performance.git
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'BenchmarksGame.FannkuchRedux_5*'
### BenchmarksGame.FannkuchRedux_5.RunBench(n: 10, expectedSum: 38) #### ETL Files #### Histogram #### JIT Disasms ### Docs [Profiling workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/profiling-workflow-dotnet-runtime.md) [Benchmarking workflow for dotnet/runtime repository](https://github.com/dotnet/performance/blob/master/docs/benchmarking-workflow-dotnet-runtime.md)
LoopedBard3 commented 2 months ago

The duration is hitting just over 200ms, the switch to more noisy and now faster execution may be due to slightly different JIT tiering each run. We should probably make this test faster or set the number of times that it runs.