dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 9/4/2026 7:52:17 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [25f20c2fd360fc0d7c126e50f7c784f8338d6faf](https://github.com/dotnet/runtime/commit/25f20c2fd360fc0d7c126e50f7c784f8338d6faf)
Compare | [aefed6dd306df5c1350a7a9b27a641a840ee16f8](https://github.com/dotnet/runtime/commit/aefed6dd306df5c1350a7a9b27a641a840ee16f8)
Diff | [Diff](https://github.com/dotnet/runtime/compare/25f20c2fd360fc0d7c126e50f7c784f8338d6faf...aefed6dd306df5c1350a7a9b27a641a840ee16f8)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Linq.Tests.Perf_Enumerable
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ToArray - 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.Linq.Tests.Perf_Enumerable*'
```
### System.Linq.Tests.Perf_Enumerable.ToArray(input: ICollection)
#### 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.Linq.Tests.Perf_Enumerable.ToArray(input: ICollection) benchmark source at performance/src/benchmarks/micro/libraries/System.Linq/Perf.Enumerable.cs#L234-L236 and review the baseline and compare commits. Run the provided benchmarks_ci.py command, then use the linked test report and regression data to investigate the change. Done means the regression is explained or corrected and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100