dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 6/20/2026 10:42:33 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 | [8a395fa3d63a95b22b1e60dfeb3263668ef9b086](https://github.com/dotnet/runtime/commit/8a395fa3d63a95b22b1e60dfeb3263668ef9b086)
Compare | [b4ca93f1d026919b29a1000cf520db442cabf61b](https://github.com/dotnet/runtime/commit/b4ca93f1d026919b29a1000cf520db442cabf61b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/8a395fa3d63a95b22b1e60dfeb3263668ef9b086...b4ca93f1d026919b29a1000cf520db442cabf61b)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.TryGetValueFalse<SmallClass, SmallClass>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [IDictionary - 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.Collections.TryGetValueFalse*'
```
### System.Collections.TryGetValueFalse<SmallClass, SmallClass>.IDictionary(Size: 512)
#### 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 benchmark source, TryGetValueFalse.cs lines 71-73, and the baseline/compare commits. Reproduce the System.Collections.TryGetValueFalse benchmark with the provided benchmarks_ci.py command, then compare the reported performance and available test reports. Done means the regression is explained and the benchmark returns to the expected performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100