dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/1/2026 4:06:20 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 | [ba804600579e7f220b5d6545e3005406d78eb36c](https://github.com/dotnet/runtime/commit/ba804600579e7f220b5d6545e3005406d78eb36c)
Compare | [f7a6366c5400f3d8b6aa882944e57d5ae37c1848](https://github.com/dotnet/runtime/commit/f7a6366c5400f3d8b6aa882944e57d5ae37c1848)
Diff | [Diff](https://github.com/dotnet/runtime/compare/ba804600579e7f220b5d6545e3005406d78eb36c...f7a6366c5400f3d8b6aa882944e57d5ae37c1848)
Configs | CompilationMode:wasm, RunKind:micro
### Regressions in System.Numerics.Tests.Perf_VectorOf<UInt64>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [LessThanAnyBenchmark - 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<UInt64>.LessThanAnyBenchmark
#### 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 source at src/benchmarks/micro/libraries/System.Numerics.Vectors/Perf_VectorOfT.cs lines 137-138 and reproduce the reported LessThanAnyBenchmark using scripts/benchmarks_ci.py with the supplied filter. Compare the baseline and test commits, then use the profiling and benchmarking workflow docs and the linked reports to identify the regression. Done means the benchmark no longer shows the reported regression and the relevant performance validation passes.
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
- 35/100