[Perf] Linux/x64: 1 Improvement on 7/23/2026 4:52:54 AM +00:00

### Run Information

Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [dc3757e67b2d6eb7d6db7e052574a02c3d445432](https://github.com/dotnet/runtime/commit/dc3757e67b2d6eb7d6db7e052574a02c3d445432)
Compare | [3e64752d437bc3429276c0cd019f30e6d4088d1f](https://github.com/dotnet/runtime/commit/3e64752d437bc3429276c0cd019f30e6d4088d1f)
Diff | [Diff](https://github.com/dotnet/runtime/compare/dc3757e67b2d6eb7d6db7e052574a02c3d445432...3e64752d437bc3429276c0cd019f30e6d4088d1f)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr

### Improvements in System.Collections.IndexerSetReverse<String>

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

• [IList - 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 'System.Collections.IndexerSetReverse*'
```

### System.Collections.IndexerSetReverse<String>.IList(Size: 512)

#### 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 the benchmark source in the dotnet/performance repository at src/benchmarks/micro/libraries/System.Collections/Indexer/IndexerSetReverse.cs#L59-L61, then read the benchmarking workflow linked in the issue. Run the provided benchmarks_ci.py command and compare the baseline and test reports; done means the reported improvement is understood and any resulting runtime work is validated by the benchmark.

Written by the indexing model from the issue text.