[Perf] Linux/x64: 1 Regression on 8/5/2026 6:23:30 AM +00:00

### Run Information

Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [f107b2325cccfd453f9bf46013159f4704ea56c2](https://github.com/dotnet/runtime/commit/f107b2325cccfd453f9bf46013159f4704ea56c2)
Compare | [b6caa7d9ec9b346b2b09a31ab3fccfe7d049b723](https://github.com/dotnet/runtime/commit/b6caa7d9ec9b346b2b09a31ab3fccfe7d049b723)
Diff | [Diff](https://github.com/dotnet/runtime/compare/f107b2325cccfd453f9bf46013159f4704ea56c2...b6caa7d9ec9b346b2b09a31ab3fccfe7d049b723)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro

### Regressions in System.Text.Json.Tests.Utf8JsonReaderCommentsTests

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

• [Utf8JsonReaderCommentParsing - 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.Text.Json.Tests.Utf8JsonReaderCommentsTests*'
```

### System.Text.Json.Tests.Utf8JsonReaderCommentsTests.Utf8JsonReaderCommentParsing(CommentHandling: Allow, SegmentSize: 100, TestCase: ShortSingleLine)

#### 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 System.Text.Json.Tests.Utf8JsonReaderCommentsTests benchmark and its source in src/benchmarks/micro/libraries/System.Text.Json/Utf8JsonReader/Utf8JsonReader.Comments.Tests.cs, then compare the listed baseline and compare commits. Run the provided benchmarks_ci.py command and inspect the linked test report; done means identifying and addressing the cause of the reported WebAssembly performance regression.

Written by the indexing model from the issue text.