[Perf] Linux/x64: 1 Improvement on 3/31/2026 12:12:38 PM +00:00

### Run Information

Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [df311e561f7f53880dfaa4b12df0eb75da8a7bce](https://github.com/dotnet/sdk/commit/df311e561f7f53880dfaa4b12df0eb75da8a7bce)
Compare | [d70206844a95b337601237466bfc6cbb7d52d6d4](https://github.com/dotnet/sdk/commit/d70206844a95b337601237466bfc6cbb7d52d6d4)
Diff | [Diff](https://github.com/dotnet/sdk/compare/df311e561f7f53880dfaa4b12df0eb75da8a7bce...d70206844a95b337601237466bfc6cbb7d52d6d4)
Configs | CompilationMode:tiered, RunKind:akadeindexedset

### Improvements in Akade.IndexedSet.Benchmarks.PrefixIndexBenchmarks

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

• [StartsWith_IndexedSet - Duration of single invocation]()
• 📝 - [Benchmark Source]()
• [ADX - Test Multi Config Graph]()

| 554.40 ns | 483.19 ns | 0.87 | 0.00 | True | | |

[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.PrefixIndexBenchmarks*'
```

### Akade.IndexedSet.Benchmarks.PrefixIndexBenchmarks.StartsWith_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)

Start with src/benchmarks/real-world/Akade.IndexedSet.Benchmarks/PrefixIndexBenchmarks.cs at lines 24-28 and review the reported StartsWith_IndexedSet comparison. Run the provided benchmarks_ci.py command using the documented benchmarking workflow, then use the linked test report and comparison data to investigate the improvement. Done means the performance result is explained and any resulting change is validated by the benchmark.

Written by the indexing model from the issue text.