dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 7/5/2026 8:38:45 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 | [a9679a8de87742e170318ea39f7f0e2874bcd441](https://github.com/dotnet/sdk/commit/a9679a8de87742e170318ea39f7f0e2874bcd441)
Compare | [02385e26e452b21a97d8a5e694fe3ada7259a582](https://github.com/dotnet/sdk/commit/02385e26e452b21a97d8a5e694fe3ada7259a582)
Diff | [Diff](https://github.com/dotnet/sdk/compare/a9679a8de87742e170318ea39f7f0e2874bcd441...02385e26e452b21a97d8a5e694fe3ada7259a582)
Configs | CompilationMode:tiered, RunKind:scenarios
### Improvements 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 docs/benchmarking-workflow-dotnet-runtime.md, then run the provided benchmarks_ci.py command for the WinForms Large FDD Publish filter. Compare the reported baseline and test results using the linked report and graph. The issue does not define a code change, so done means determining whether the improvement is reproducible and what actionable change, if any, is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100