dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 6/11/2026 11:26:48 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 | [f59cad6eaf5bbe1c3da6aea07e998f686c0ef0bd](https://github.com/dotnet/runtime/commit/f59cad6eaf5bbe1c3da6aea07e998f686c0ef0bd)
Compare | [2f3821520acb47a26220fe08ee13cb89b3a38572](https://github.com/dotnet/runtime/commit/2f3821520acb47a26220fe08ee13cb89b3a38572)
Diff | [Diff](https://github.com/dotnet/runtime/compare/f59cad6eaf5bbe1c3da6aea07e998f686c0ef0bd...2f3821520acb47a26220fe08ee13cb89b3a38572)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in System.Collections.ContainsTrueComparer<String>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [FrozenSet - 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.ContainsTrueComparer*'
```
### System.Collections.ContainsTrueComparer<String>.FrozenSet(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 in performance/src/benchmarks/micro/libraries/System.Collections/Contains/ContainsTrueComparer.cs at lines 115-124 and compare the listed baseline and test commits. Run the provided benchmarks_ci.py command, then inspect the linked test report and performance history to confirm the FrozenSet regression. Done means the regression is explained and the issue has a documented disposition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ubuntu, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100