dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 6/21/2026 8:44:07 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [a065c06c0c5f5647d8e312fc70dec3f5ca77b830](https://github.com/dotnet/sdk/commit/a065c06c0c5f5647d8e312fc70dec3f5ca77b830)
Compare | [b756a8d8a0e64905e16c81911bb09a8110bc3395](https://github.com/dotnet/sdk/commit/b756a8d8a0e64905e16c81911bb09a8110bc3395)
Diff | [Diff](https://github.com/dotnet/sdk/compare/a065c06c0c5f5647d8e312fc70dec3f5ca77b830...b756a8d8a0e64905e16c81911bb09a8110bc3395)
Configs | CompilationMode:tiered, RunKind:scenarios
### Regressions in Startup - WinForms Large - FDD Publish
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Startup - WinForms Large - FDD Publish - Generic Startup]()
- [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 'Startup - WinForms Large - FDD Publish*'
```
### Startup - WinForms Large - FDD Publish
#### 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 follow the benchmarking workflow in dotnet/performance. Run benchmarks_ci.py with the provided WinForms Large FDD Publish filter and inspect the linked report and graph. Done means identifying and addressing the startup regression, then confirming the benchmark no longer regresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100