dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/26/2026 4:02:35 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 | [8baacb006f5615ebd705bdf9de98ca5df7bf1ba1](https://github.com/dotnet/runtime/commit/8baacb006f5615ebd705bdf9de98ca5df7bf1ba1)
Compare | [08df03ba6493589f3816e193847b50f105bf4c7a](https://github.com/dotnet/runtime/commit/08df03ba6493589f3816e193847b50f105bf4c7a)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8baacb006f5615ebd705bdf9de98ca5df7bf1ba1...08df03ba6493589f3816e193847b50f105bf4c7a)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Buffers.Text.Tests.Utf8FormatterTests
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [FormatterUInt32 - 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.FormatterUInt32(value: 0)
#### 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 benchmark source at src/benchmarks/micro/libraries/System.Buffers/Utf8FormatterTests.cs:40-42 and run the provided benchmarks_ci.py command. Compare the reported baseline and test results, then inspect the linked benchmark and test reports to determine whether the improvement has an actionable cause or change; the issue does not define a specific implementation target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100