dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 6/16/2026 6:17: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 | [98d5787a726f050c592e7c126c6ab62b1954288c](https://github.com/dotnet/runtime/commit/98d5787a726f050c592e7c126c6ab62b1954288c)
Compare | [4b211ba77ff3bfa4b7d2ba0c873e6bd337b6c6f0](https://github.com/dotnet/runtime/commit/4b211ba77ff3bfa4b7d2ba0c873e6bd337b6c6f0)
Diff | [Diff](https://github.com/dotnet/runtime/compare/98d5787a726f050c592e7c126c6ab62b1954288c...4b211ba77ff3bfa4b7d2ba0c873e6bd337b6c6f0)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Runtime.Intrinsics.Tests.Perf_Vector128Of<Single>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [MinBenchmark - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config 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<Single>.MinBenchmark
#### 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 System.Runtime.Intrinsics.Tests.Perf_Vector128OfT benchmark source at src/benchmarks/micro/libraries/System.Runtime.Intrinsics/Perf_Vector128OfT.cs#L148-L149 and compare the baseline and regression commits. Reproduce with scripts/benchmarks_ci.py using the supplied filter and inspect the linked test report. Done means identifying and validating the cause of the wasm AOT performance regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100