dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Regressions on 8/5/2026 6:23:30 AM +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 | [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.Buffers.Text.Tests.Utf8FormatterTests
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [FormatterInt32 - 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.Buffers.Text.Tests.Utf8FormatterTests*'
```
### System.Buffers.Text.Tests.Utf8FormatterTests.FormatterInt32(value: 2147483647)
#### 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)
---
### 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)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked benchmark sources for Utf8FormatterTests.cs and Utf8JsonReader.Comments.Tests.cs, then review the baseline and compare commits in the regression reports. Run the documented benchmarks with the provided filters under AOT and WebAssembly, and use the profiling workflow if needed. Done means identifying and addressing the cause of both regressions and confirming the benchmark results no longer regress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100