dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 8/28/2026 6:27:02 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [57c9c3fdcbc94ad98f0a4b8abedb7c6eadfb264b](https://github.com/dotnet/runtime/commit/57c9c3fdcbc94ad98f0a4b8abedb7c6eadfb264b)
Compare | [d2ea726dd3d8faad797755c9fbb1ff15226e25f0](https://github.com/dotnet/runtime/commit/d2ea726dd3d8faad797755c9fbb1ff15226e25f0)
Diff | [Diff](https://github.com/dotnet/runtime/compare/57c9c3fdcbc94ad98f0a4b8abedb7c6eadfb264b...d2ea726dd3d8faad797755c9fbb1ff15226e25f0)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Tests.Perf_Array
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ArrayRetrieve2D - 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
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Tests.Perf_Array*'
```
### System.Tests.Perf_Array.ArrayRetrieve2D
#### 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.Tests.Perf_Array.ArrayRetrieve2D benchmark source linked at src/benchmarks/micro/libraries/System.Runtime/Perf.Array.cs#L165-L#L189 and the listed baseline and compare commits. Run the provided benchmarks_ci.py command on Windows, then use the linked test report and profiling workflow to investigate the regression. Done means the cause is identified and the reported performance change is addressed or explained.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100