dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 5/18/2026 9:55:52 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 | [bb4ef64bceda7720966963cd9de4f334833b5f25](https://github.com/dotnet/runtime/commit/bb4ef64bceda7720966963cd9de4f334833b5f25)
Compare | [c00becf82d1f6135f1d0a5323ece70817de9b09a](https://github.com/dotnet/runtime/commit/c00becf82d1f6135f1d0a5323ece70817de9b09a)
Diff | [Diff](https://github.com/dotnet/runtime/compare/bb4ef64bceda7720966963cd9de4f334833b5f25...c00becf82d1f6135f1d0a5323ece70817de9b09a)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in Benchstone.BenchI.EightQueens
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Test - 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 'Benchstone.BenchI.EightQueens*'
```
### Benchstone.BenchI.EightQueens.Test
#### 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/micro/runtime/Benchstones/BenchI/8Queens.cs and reproduce Benchstone.BenchI.EightQueens with the provided benchmarks_ci.py command. Compare the baseline and regression commits, then use the linked test report and profiling workflow to identify the cause. Done means the regression is explained and corrected, with the benchmark no longer showing the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, ubuntu, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100