dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/19/2026 9:49:55 PM +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 | [4c9e771cbd5e35313cef06c4d7efb55070fd5493](https://github.com/dotnet/runtime/commit/4c9e771cbd5e35313cef06c4d7efb55070fd5493)
Compare | [563abf220847ed66cab58f0d7d166cb264874f40](https://github.com/dotnet/runtime/commit/563abf220847ed66cab58f0d7d166cb264874f40)
Diff | [Diff](https://github.com/dotnet/runtime/compare/4c9e771cbd5e35313cef06c4d7efb55070fd5493...563abf220847ed66cab58f0d7d166cb264874f40)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Buffers.Text.Tests.Utf8ParserTests
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [TryParseDouble - 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.Utf8ParserTests*'
```
### System.Buffers.Text.Tests.Utf8ParserTests.TryParseDouble(value: -1.7976931348623157e+308)
#### 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 by running the linked benchmarks_ci.py command with the System.Buffers.Text.Tests.Utf8ParserTests filter, then compare the baseline and test commits listed in the issue. Read the benchmark source at src/benchmarks/micro/libraries/System.Buffers/Utf8ParserTests.cs around lines 109-112 and use the linked test report to investigate the TryParseDouble regression. Done means the regression is understood and the benchmark returns to its prior performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, ubuntu, wasm
- Domain
- operating-systems, performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100