dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 7/12/2026 12:03:31 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [a7ed27ba3f7a0a32634be47079ac659909797806](https://github.com/dotnet/runtime/commit/a7ed27ba3f7a0a32634be47079ac659909797806)
Compare | [010acabe079d1bd50f838de34e9815f81d977469](https://github.com/dotnet/runtime/commit/010acabe079d1bd50f838de34e9815f81d977469)
Diff | [Diff](https://github.com/dotnet/runtime/compare/a7ed27ba3f7a0a32634be47079ac659909797806...010acabe079d1bd50f838de34e9815f81d977469)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in Benchstone.BenchI.CSieve
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
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'Benchstone.BenchI.CSieve*'
```
### Benchstone.BenchI.CSieve.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 the Benchstone.BenchI.CSieve source in performance/src/benchmarks/micro/runtime/Benchstones/BenchI/CSieve.cs and the linked baseline/compare commits. Run the provided benchmarks_ci.py command and consult the benchmarking workflow documentation to reproduce the Windows/x64 regression. Done means the reported slowdown is reproduced and its cause and resolution are validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100