dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 7/15/2026 9:23:09 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 | [9b4d3b99c89873c850b8ec1f7fd4b66d9eb6e3e2](https://github.com/dotnet/sdk/commit/9b4d3b99c89873c850b8ec1f7fd4b66d9eb6e3e2)
Compare | [ecc427bc7d7b4ee32b943f71196ab377f67c1105](https://github.com/dotnet/sdk/commit/ecc427bc7d7b4ee32b943f71196ab377f67c1105)
Diff | [Diff](https://github.com/dotnet/sdk/compare/9b4d3b99c89873c850b8ec1f7fd4b66d9eb6e3e2...ecc427bc7d7b4ee32b943f71196ab377f67c1105)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Regressions in Akade.IndexedSet.Benchmarks.MultiValueIndexBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Multivalue_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.MultiValueIndexBenchmarks*'
```
### Akade.IndexedSet.Benchmarks.MultiValueIndexBenchmarks.Multivalue_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
Run the supplied benchmarks_ci.py command for Akade.IndexedSet.Benchmarks.MultiValueIndexBenchmarks and inspect MultiValueIndexBenchmarks.cs. Compare the baseline and test commits, then use the linked test report and profiling workflow to identify the regression. Done means the performance change is explained and an appropriate correction or follow-up is recorded.
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