dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/1/2026 12:21:46 AM +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 | [44687f2d763be239ff562b137360ab572f47066e](https://github.com/dotnet/runtime/commit/44687f2d763be239ff562b137360ab572f47066e)
Compare | [0eb5481340ea675857c7a7abf18f68a60b52a686](https://github.com/dotnet/runtime/commit/0eb5481340ea675857c7a7abf18f68a60b52a686)
Diff | [Diff](https://github.com/dotnet/runtime/compare/44687f2d763be239ff562b137360ab572f47066e...0eb5481340ea675857c7a7abf18f68a60b52a686)
Configs | CompilationMode:wasm, RunKind:micro
### Regressions in System.Numerics.Tests.Perf_VectorOf<UInt16>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [GreaterThanOrEqualAllBenchmark - 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.Numerics.Tests.Perf_VectorOf*'
```
### System.Numerics.Tests.Perf_VectorOf<UInt16>.GreaterThanOrEqualAllBenchmark
#### 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 by running the documented benchmarks_ci.py command with the System.Numerics.Tests.Perf_VectorOf* filter. Compare the baseline and compare commits, inspect the benchmark source at dotnet/performance/src/benchmarks/micro/libraries/System.Numerics.Vectors/Perf_VectorOfT.cs#L125-L126, and review the linked test report and IR data. Done means the WASM benchmark regression is explained and resolved without introducing a new performance loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100