dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 3/17/2026 1:26:21 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 | [c12d1f565f615d5d48ff443858a67ac148a3bd8b](https://github.com/dotnet/sdk/commit/c12d1f565f615d5d48ff443858a67ac148a3bd8b)
Compare | [3ccdcc4cf9b93bf3504275d4506144cf68c15b2c](https://github.com/dotnet/sdk/commit/3ccdcc4cf9b93bf3504275d4506144cf68c15b2c)
Diff | [Diff](https://github.com/dotnet/sdk/compare/c12d1f565f615d5d48ff443858a67ac148a3bd8b...3ccdcc4cf9b93bf3504275d4506144cf68c15b2c)
Configs | CompilationMode:tiered, RunKind:akadeindexedset
### Regressions in Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [FuzzyContains_IndexedSet - 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 'Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks*'
```
### Akade.IndexedSet.Benchmarks.FullTextIndexBenchmarks.FuzzyContains_IndexedSet
#### 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 src/benchmarks/real-world/Akade.IndexedSet.Benchmarks/FullTextIndexBenchmarks.cs at lines 32-36, then run the benchmarks_ci.py command from the reproduction section for FuzzyContains_IndexedSet. Compare the listed baseline and test commits and inspect the linked report to determine whether the regression is reproducible and what triage or fix is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, python
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100