dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 6/23/2026 11:08:11 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 | [2d748ca0a1e035e7b7c5bfb74e944b26a8df654b](https://github.com/dotnet/sdk/commit/2d748ca0a1e035e7b7c5bfb74e944b26a8df654b)
Compare | [4f6d02131fae05b5de421f33e38dc73906ef5aca](https://github.com/dotnet/sdk/commit/4f6d02131fae05b5de421f33e38dc73906ef5aca)
Diff | [Diff](https://github.com/dotnet/sdk/compare/2d748ca0a1e035e7b7c5bfb74e944b26a8df654b...4f6d02131fae05b5de421f33e38dc73906ef5aca)
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 performance repository's scripts/benchmarks_ci.py command in the Repro section, using the Startup - PaintDotNet - FDD Publish filter. Compare the linked baseline and test reports and consult the benchmarking and profiling workflow documents. Done means identifying and addressing the reported Windows/x64 startup regression, then confirming the benchmark result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100