dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 7/31/2026 9:30:32 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 | [8c1bd18b8c65722ac42857e5bb2fe68d67f9f63d](https://github.com/dotnet/sdk/commit/8c1bd18b8c65722ac42857e5bb2fe68d67f9f63d)
Compare | [bfb5366c2c6e45c00cd194bc21c623d32fcd4066](https://github.com/dotnet/sdk/commit/bfb5366c2c6e45c00cd194bc21c623d32fcd4066)
Diff | [Diff](https://github.com/dotnet/sdk/compare/8c1bd18b8c65722ac42857e5bb2fe68d67f9f63d...bfb5366c2c6e45c00cd194bc21c623d32fcd4066)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Paging_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.Paging_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 around lines 38-42 and reproduce the reported benchmark using the provided benchmarks_ci.py command. Compare the baseline and test commits and inspect the linked test report to determine the regression's cause. Done means the regression is understood and the benchmark result is verified after the relevant change.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100