dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/13/2026 3:15:10 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 | [8df98c4d2d17bcba98193afa9ae2e72908921f86](https://github.com/dotnet/runtime/commit/8df98c4d2d17bcba98193afa9ae2e72908921f86)
Compare | [db330a0e1ac8c7950a07271b2a5d8ac1830243bf](https://github.com/dotnet/runtime/commit/db330a0e1ac8c7950a07271b2a5d8ac1830243bf)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8df98c4d2d17bcba98193afa9ae2e72908921f86...db330a0e1ac8c7950a07271b2a5d8ac1830243bf)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Buffers.Text.Tests.Utf8ParserTests
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [TryParseDecimal - 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.TryParseDecimal(value: 123456.789)
#### 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 source at src/benchmarks/micro/libraries/System.Buffers/Utf8ParserTests.cs#L101-L104 and reproduce the result using the provided benchmarks_ci.py command. Compare the baseline and compare commits, then use the linked test report and history graph to investigate TryParseDecimal. Done means the reported regression is understood and the benchmark no longer shows the performance drop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100