[Perf] Linux/x64: 1 Regression on 8/13/2026 4:11:41 PM +00:00

### Run Information

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

### Regressions in System.Collections.CreateAddAndClear<String>

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

• [SortedDictionary - 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.CreateAddAndClear*'
```

### System.Collections.CreateAddAndClear<String>.SortedDictionary(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 src/benchmarks/micro/libraries/System.Collections/CreateAddAndClear.cs at lines 156-166 and the profiling or benchmarking workflow linked in the issue. Run the provided benchmarks_ci.py command, then compare the baseline and test commits and inspect the linked test report. Done means the Linux/x64 WASM regression is explained and the benchmark result is restored or otherwise resolved.

Written by the indexing model from the issue text.