dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 6/19/2026 8:51:35 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 | [a50a8baa52210e32fb688a6cb7f59e40b79ff830](https://github.com/dotnet/sdk/commit/a50a8baa52210e32fb688a6cb7f59e40b79ff830)
Compare | [ae899ea0758628a22feb37a1401ae397cc5fc8d1](https://github.com/dotnet/sdk/commit/ae899ea0758628a22feb37a1401ae397cc5fc8d1)
Diff | [Diff](https://github.com/dotnet/sdk/compare/a50a8baa52210e32fb688a6cb7f59e40b79ff830...ae899ea0758628a22feb37a1401ae397cc5fc8d1)
Configs | CompilationMode:tiered, RunKind:scenarios
### Regressions in Startup - PaintDotNet - FDD Publish
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Startup - PaintDotNet - 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 - PaintDotNet - FDD Publish*'
```
### Startup - PaintDotNet - 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-to-compare diff and the benchmarking workflow documentation. Run the provided benchmarks_ci.py command with the PaintDotNet FDD Publish filter on Windows, then inspect the linked test report and regression graph. Done means reproducing the startup regression and documenting its cause or triage status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems, performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100