dotnet / dotnet/perf-autofiling-issues

[Perf] Linux/arm64: 1 Regression on 8/4/2026 8:53:30 PM +00:00

Open
#77,844 1 comment 0 reactions 0 assignees View on GitHub
arch-arm64 bdn-update branch-refs/heads/main compilationmode-tiered kind-sve Noise os-linux perf-regression runkind-sve runtime-coreclr untriaged
Dominant language
No language data
Stars
10
Forks
8
PR merge metrics
PR metrics pending

Description

### Run Information

Name | Value
-- | --
Architecture | arm64
OS | azurelinux 3.0
Queue | CobaltAzureLinux
Baseline | [2dd5330804f9d4f49599d82c90a67892d4dd8af0](https://github.com/dotnet/runtime/commit/2dd5330804f9d4f49599d82c90a67892d4dd8af0)
Compare | [173e6b40e02cd1652102c09e07bd4cf7320b3d4d](https://github.com/dotnet/runtime/commit/173e6b40e02cd1652102c09e07bd4cf7320b3d4d)
Diff | [Diff](https://github.com/dotnet/runtime/compare/2dd5330804f9d4f49599d82c90a67892d4dd8af0...173e6b40e02cd1652102c09e07bd4cf7320b3d4d)
Configs | CompilationMode:tiered, RunKind:sve

### Regressions in SveBenchmarks.PairwiseAdd

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

  • [Vector128PairwiseAdd - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 4.40 μs | 4.78 μs | 1.09 | 0.21 | False | | |

![graph]()
[Test Report]()

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

```cmd
git clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'SveBenchmarks.PairwiseAdd*'
```

### SveBenchmarks.PairwiseAdd.Vector128PairwiseAdd(Size: 10015)

#### 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)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the benchmark command in the Repro section and inspect dotnet/performance/src/benchmarks/micro/sve/PairwiseAdd.cs lines 76-107. Compare the listed baseline and test commits, then use the linked report or profiling workflow to investigate the arm64 regression. Done means the Vector128PairwiseAdd result no longer regresses under the stated tiered SVE configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp, linux
Domain
operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.