dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 7/28/2026 8:32:51 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 | [4d07108c0125e4741bda596f27740118c0fe3833](https://github.com/dotnet/runtime/commit/4d07108c0125e4741bda596f27740118c0fe3833)
Compare | [00fc09ea5b2e39c46d56fda130b6693e07d449d8](https://github.com/dotnet/runtime/commit/00fc09ea5b2e39c46d56fda130b6693e07d449d8)
Diff | [Diff](https://github.com/dotnet/runtime/compare/4d07108c0125e4741bda596f27740118c0fe3833...00fc09ea5b2e39c46d56fda130b6693e07d449d8)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Tests.Perf_Uri
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [UnescapeDataString - 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_Uri*'
```
### System.Tests.Perf_Uri.UnescapeDataString(input: "%E4%BD%A0%E5%A5%BD")
#### 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 System.Tests.Perf_Uri benchmark and its source in dotnet/performance/src/benchmarks/micro/libraries/System.Runtime/Perf.Uri.cs. Run the provided benchmarks_ci.py command, compare the baseline and test commits, and use the report links to identify the cause; done means the UnescapeDataString regression is explained and resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100