dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 9/15/2026 12:42:06 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 | [c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da](https://github.com/dotnet/sdk/commit/c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da)
Compare | [1c83110633092213f4f794b69557f885a96e7a08](https://github.com/dotnet/sdk/commit/1c83110633092213f4f794b69557f885a96e7a08)
Diff | [Diff](https://github.com/dotnet/sdk/compare/c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da...1c83110633092213f4f794b69557f885a96e7a08)
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 at lines 44-48 and review the linked baseline/compare commits. Run the provided benchmarks_ci.py command on Windows and inspect the generated report for Min_IndexedSet. Done means identifying and resolving the cause of the reported performance regression, with the benchmark no longer showing the regression.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100