dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 8/22/2026 9:21:19 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 | [19bc97f3dd3ab67c7810e4ab179125b7c6a60641](https://github.com/dotnet/sdk/commit/19bc97f3dd3ab67c7810e4ab179125b7c6a60641)
Compare | [b8c18a5c2f5d06efdd635120822953728b21678e](https://github.com/dotnet/sdk/commit/b8c18a5c2f5d06efdd635120822953728b21678e)
Diff | [Diff](https://github.com/dotnet/sdk/compare/19bc97f3dd3ab67c7810e4ab179125b7c6a60641...b8c18a5c2f5d06efdd635120822953728b21678e)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Regressions in Akade.IndexedSet.Benchmarks.RangeIndexBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Min_IndexedSet - 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 'Akade.IndexedSet.Benchmarks.RangeIndexBenchmarks*'
```
### Akade.IndexedSet.Benchmarks.RangeIndexBenchmarks.Min_IndexedSet
#### 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 src/benchmarks/real-world/Akade.IndexedSet.Benchmarks/RangeIndexBenchmarks.cs lines 44-48 and reproduce the reported benchmark with the benchmarks_ci.py command. Compare the baseline and test commits and inspect the linked benchmark and test reports to determine the source of the Windows/x64 regression. Done means the cause is identified and the Min_IndexedSet regression is resolved or triaged with supporting measurements.
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
- Needs clarification
- Newbie friendliness
- 35/100