dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 6/25/2026 10:59: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 | [b756a8d8a0e64905e16c81911bb09a8110bc3395](https://github.com/dotnet/sdk/commit/b756a8d8a0e64905e16c81911bb09a8110bc3395)
Compare | [1d4910780fe728cf5affade170fe51fc8f96f9fb](https://github.com/dotnet/sdk/commit/1d4910780fe728cf5affade170fe51fc8f96f9fb)
Diff | [Diff](https://github.com/dotnet/sdk/compare/b756a8d8a0e64905e16c81911bb09a8110bc3395...1d4910780fe728cf5affade170fe51fc8f96f9fb)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Regressions in Akade.IndexedSet.Benchmarks.UniqueIndexBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Unique_IndexedSet_Single - 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.UniqueIndexBenchmarks*'
```
### Akade.IndexedSet.Benchmarks.UniqueIndexBenchmarks.Unique_IndexedSet_Single
#### 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/UniqueLookupBenchmarks.cs lines 40-49 and reproduce the benchmark with the provided benchmarks_ci.py command. Compare the baseline and test commits and use the linked report to determine whether the 33% regression reproduces; done means identifying and addressing its cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100