dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 7/13/2026 9:23:20 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 | [ca60c43d982bb8e171b66ef8a38a777e004768ba](https://github.com/dotnet/sdk/commit/ca60c43d982bb8e171b66ef8a38a777e004768ba)
Compare | [50dbab4de210e882172b07934e9666313b7065f1](https://github.com/dotnet/sdk/commit/50dbab4de210e882172b07934e9666313b7065f1)
Diff | [Diff](https://github.com/dotnet/sdk/compare/ca60c43d982bb8e171b66ef8a38a777e004768ba...50dbab4de210e882172b07934e9666313b7065f1)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Improvements 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 and the linked Unique_IndexedSet_Single report, then review the baseline and compare commits. Run the provided benchmarks_ci.py command using the documented benchmarking workflow. Done means determining whether the reported improvement needs follow-up and recording the triage result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git, python
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100