dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/31/2026 6:09:14 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 | [aa036afce592ad80e938a35bd376222fb232cba9](https://github.com/dotnet/runtime/commit/aa036afce592ad80e938a35bd376222fb232cba9)
Compare | [3b2b97b454ad0e3627f4fbc118f0284cb0ab07b5](https://github.com/dotnet/runtime/commit/3b2b97b454ad0e3627f4fbc118f0284cb0ab07b5)
Diff | [Diff](https://github.com/dotnet/runtime/compare/aa036afce592ad80e938a35bd376222fb232cba9...3b2b97b454ad0e3627f4fbc118f0284cb0ab07b5)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in System.Tests.Perf_Int32
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ParseHex - 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.Tests.Perf_Int32*'
```
### System.Tests.Perf_Int32.ParseHex(value: "3039")
#### 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 src/benchmarks/micro/libraries/System.Runtime/Perf.Int32.cs, focusing on ParseHex, and compare the linked baseline and test commits. Run the documented benchmarks_ci.py command with the System.Tests.Perf_Int32 filter, then use the benchmarking and profiling workflow reports to confirm the regression. Done means the regression is explained and the benchmark returns to the expected performance level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100