dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 7/9/2026 12:24:40 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 | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [b4b350a66ea5dcf13420747036d8b263cdf6cbef](https://github.com/dotnet/sdk/commit/b4b350a66ea5dcf13420747036d8b263cdf6cbef)
Compare | [c7028b23fb9d8e1f786cc404c6107c53a0d3a2a3](https://github.com/dotnet/sdk/commit/c7028b23fb9d8e1f786cc404c6107c53a0d3a2a3)
Diff | [Diff](https://github.com/dotnet/sdk/compare/b4b350a66ea5dcf13420747036d8b263cdf6cbef...c7028b23fb9d8e1f786cc404c6107c53a0d3a2a3)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Improvements in Akade.IndexedSet.Benchmarks.RangeIndexBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Paging_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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'Akade.IndexedSet.Benchmarks.RangeIndexBenchmarks*'
```
### Akade.IndexedSet.Benchmarks.RangeIndexBenchmarks.Paging_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 38-42 and read the benchmarking workflow documentation. Run the provided benchmarks_ci.py command with the listed filter, then compare the generated result with the linked baseline and test reports. Done means the improvement is reproducible and its cause or required follow-up is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100