dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 8/14/2026 9:50: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 | [283314d5d7f2d77d1a31087ec962a4c407106445](https://github.com/dotnet/sdk/commit/283314d5d7f2d77d1a31087ec962a4c407106445)
Compare | [7cdb217445905f3342bbb0266a4497b9a014389a](https://github.com/dotnet/sdk/commit/7cdb217445905f3342bbb0266a4497b9a014389a)
Diff | [Diff](https://github.com/dotnet/sdk/compare/283314d5d7f2d77d1a31087ec962a4c407106445...7cdb217445905f3342bbb0266a4497b9a014389a)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Regressions in Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Contains_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.FullTextIndexBenchmarks*'
```
### Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks.Contains_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/FullTextIndexBenchmarks.cs and reproduce the Contains_IndexedSet result using the provided benchmarks_ci.py command. Compare the baseline and compare commits and inspect the linked performance report to determine the source of the regression; done means the cause is identified and the benchmark result is addressed.
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