dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 7/31/2026 9:13:23 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 | [8c1bd18b8c65722ac42857e5bb2fe68d67f9f63d](https://github.com/dotnet/sdk/commit/8c1bd18b8c65722ac42857e5bb2fe68d67f9f63d)
Compare | [bfb5366c2c6e45c00cd194bc21c623d32fcd4066](https://github.com/dotnet/sdk/commit/bfb5366c2c6e45c00cd194bc21c623d32fcd4066)
Diff | [Diff](https://github.com/dotnet/sdk/compare/8c1bd18b8c65722ac42857e5bb2fe68d67f9f63d...bfb5366c2c6e45c00cd194bc21c623d32fcd4066)
Configs | CompilationMode:tiered, RunKind:scenarios
### Regressions in Startup - PaintDotNet - FDD Publish - Affinity 85
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Startup - PaintDotNet - FDD Publish - Affinity 85 - 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 - PaintDotNet - FDD Publish - Affinity 85*'
```
### Startup - PaintDotNet - FDD Publish - Affinity 85
#### 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 benchmark command in the issue and the performance repository's docs/benchmarking-workflow-dotnet-runtime.md. Run the PaintDotNet FDD Publish benchmark, then inspect the linked history and report comparing the baseline and test commits. Done means identifying and addressing the startup regression and 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
- Needs clarification
- Newbie friendliness
- 35/100