dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Regression on 7/13/2026 9:05:18 AM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [ca60c43d982bb8e171b66ef8a38a777e004768ba](https://github.com/dotnet/sdk/commit/ca60c43d982bb8e171b66ef8a38a777e004768ba)
Compare | [50dbab4de210e882172b07934e9666313b7065f1](https://github.com/dotnet/sdk/commit/50dbab4de210e882172b07934e9666313b7065f1)
Diff | [Diff](https://github.com/dotnet/sdk/compare/ca60c43d982bb8e171b66ef8a38a777e004768ba...50dbab4de210e882172b07934e9666313b7065f1)
Configs | CompilationMode:tiered, RunKind:sdk_scenarios
### Regressions in SDK F# Console Template Clean Build
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SDK F# Console Template Clean Build - Process Time]()
- [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 'SDK F# Console Template Clean Build*'
```
### SDK F# Console Template Clean Build
#### 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 baseline and compare commits, then run the provided benchmarks_ci.py command for the SDK F# Console Template Clean Build scenario. Review the linked performance report and diff to identify the source of the 5% Windows x86 regression. Done means the regression has a documented cause and a verified resolution or disposition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, git, python
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100