dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/24/2026 1:18:54 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 | [75cffcef7186a6a0b738f15a98d0b28c6c8e6507](https://github.com/dotnet/runtime/commit/75cffcef7186a6a0b738f15a98d0b28c6c8e6507)
Compare | [d5d5cbcba8af2882afdda08e5b667206c7dbf09a](https://github.com/dotnet/runtime/commit/d5d5cbcba8af2882afdda08e5b667206c7dbf09a)
Diff | [Diff](https://github.com/dotnet/runtime/compare/75cffcef7186a6a0b738f15a98d0b28c6c8e6507...d5d5cbcba8af2882afdda08e5b667206c7dbf09a)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.Perf_SingleCharFrozenDictionary
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ToFrozenDictionary - Duration of single invocation]()
- [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.Collections.Perf_SingleCharFrozenDictionary*'
```
### System.Collections.Perf_SingleCharFrozenDictionary.ToFrozenDictionary(Count: 1000)
#### 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 reported System.Collections.Perf_SingleCharFrozenDictionary.ToFrozenDictionary benchmark, its baseline and compare commits, and the linked test report. Reproduce it using the provided benchmarks_ci.py command and inspect the performance report; done means identifying and addressing the reported regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100