dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/20/2026 2:22:01 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 | [563abf220847ed66cab58f0d7d166cb264874f40](https://github.com/dotnet/runtime/commit/563abf220847ed66cab58f0d7d166cb264874f40)
Compare | [73a9e0a51ed85481b7f03ca3f2696e020365afd6](https://github.com/dotnet/runtime/commit/73a9e0a51ed85481b7f03ca3f2696e020365afd6)
Diff | [Diff](https://github.com/dotnet/runtime/compare/563abf220847ed66cab58f0d7d166cb264874f40...73a9e0a51ed85481b7f03ca3f2696e020365afd6)
Configs | CompilationMode:wasm, RunKind:micro
### Regressions in System.Numerics.Tests.Perf_Matrix3x2
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [NegationOperatorBenchmark - 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_Matrix3x2*'
```
### System.Numerics.Tests.Perf_Matrix3x2.NegationOperatorBenchmark
#### 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 linked benchmark source, dotnet/performance/src/benchmarks/micro/libraries/System.Numerics.Vectors/Perf_Matrix3x2.cs, and compare the baseline and test commits. Run the provided benchmarks_ci.py command and inspect the linked regression report and graph. Done means identifying the cause of the NegationOperatorBenchmark slowdown and confirming the regression is resolved.
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