dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Regressions on 5/18/2026 1:06:36 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [f44c762122923c69a9c1072517492c2b7460690f](https://github.com/dotnet/runtime/commit/f44c762122923c69a9c1072517492c2b7460690f)
Compare | [f41aba36d821378cab52741e15e4ab7446b7929e](https://github.com/dotnet/runtime/commit/f41aba36d821378cab52741e15e4ab7446b7929e)
Diff | [Diff](https://github.com/dotnet/runtime/compare/f44c762122923c69a9c1072517492c2b7460690f...f41aba36d821378cab52741e15e4ab7446b7929e)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Runtime.Intrinsics.Tests.Perf_Vector128Of<SByte>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [BitwiseOrOperatorBenchmark - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [ExclusiveOrOperatorBenchmark - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
![graph]()
![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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Runtime.Intrinsics.Tests.Perf_Vector128Of*'
```
### System.Runtime.Intrinsics.Tests.Perf_Vector128Of<SByte>.BitwiseOrOperatorBenchmark
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Runtime.Intrinsics.Tests.Perf_Vector128Of<SByte>.ExclusiveOrOperatorBenchmark
#### 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 src/benchmarks/micro/libraries/System.Runtime.Intrinsics/Perf_Vector128OfT.cs lines 49-50 and 58-59, then run the provided benchmarks_ci.py command using the documented benchmarking workflow. Compare the baseline and test commits and inspect the linked reports and graphs for both wasm AOT benchmarks. Done means the regression is explained and the reported slowdown is no longer present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ubuntu, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100