dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 3/19/2026 2:48:42 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 | [01ee086359f0b721e47c9746aba5d8e95f7de970](https://github.com/dotnet/runtime/commit/01ee086359f0b721e47c9746aba5d8e95f7de970)
Compare | [1f751dacd08cf7599c64d7c243c52f85c54cb979](https://github.com/dotnet/runtime/commit/1f751dacd08cf7599c64d7c243c52f85c54cb979)
Diff | [Diff](https://github.com/dotnet/runtime/compare/01ee086359f0b721e47c9746aba5d8e95f7de970...1f751dacd08cf7599c64d7c243c52f85c54cb979)
Configs | CompilationMode:wasm, RunKind:micro
### Regressions in System.Text.RegularExpressions.Tests.Perf_Regex_Common
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [CtorInvoke - 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.Text.RegularExpressions.Tests.Perf_Regex_Common*'
```
### System.Text.RegularExpressions.Tests.Perf_Regex_Common.CtorInvoke(Options: Compiled)
#### 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.Text.RegularExpressions/Perf.Regex.Common.cs and the benchmarking workflow linked in the issue. Run the provided benchmarks_ci.py command for Perf_Regex_Common, then compare the baseline and test commits and inspect the linked report. Done means confirming and triaging the CtorInvoke compiled-regex regression with evidence for the next fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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
- 38/100