dotnet / dotnet/perf-autofiling-issues

[Perf] Windows/x64: 2 Regressions on 6/17/2026 8:59:27 AM +00:00

Open
#74,704 1 comment 0 reactions 0 assignees View on GitHub
arch-x64 branch-11.0 compilationmode-tiered kind-scenarios Look Again os-windows perf-regression runkind-scenarios untriaged
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 | [f0130b9b5627afa36f53d339e6788a4a1783d08f](https://github.com/dotnet/sdk/commit/f0130b9b5627afa36f53d339e6788a4a1783d08f)
Compare | [a50a8baa52210e32fb688a6cb7f59e40b79ff830](https://github.com/dotnet/sdk/commit/a50a8baa52210e32fb688a6cb7f59e40b79ff830)
Diff | [Diff](https://github.com/dotnet/sdk/compare/f0130b9b5627afa36f53d339e6788a4a1783d08f...a50a8baa52210e32fb688a6cb7f59e40b79ff830)
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]()
| 1035.11 ms | 1122.52 ms | 1.08 | 0.00 | True | | |

![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)

---

### Run Information

Name | Value
-- | --
Architecture | x64
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [f0130b9b5627afa36f53d339e6788a4a1783d08f](https://github.com/dotnet/sdk/commit/f0130b9b5627afa36f53d339e6788a4a1783d08f)
Compare | [a50a8baa52210e32fb688a6cb7f59e40b79ff830](https://github.com/dotnet/sdk/commit/a50a8baa52210e32fb688a6cb7f59e40b79ff830)
Diff | [Diff](https://github.com/dotnet/sdk/compare/f0130b9b5627afa36f53d339e6788a4a1783d08f...a50a8baa52210e32fb688a6cb7f59e40b79ff830)
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]()
| 919.38 ms | 967.86 ms | 1.05 | 0.00 | True | | |

![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 linked baseline and compare commits, the two benchmark reports, and docs/benchmarking-workflow-dotnet-runtime.md. Run the supplied performance/scripts/benchmarks_ci.py commands for both named startup benchmarks, then compare the results with the reported regressions. Done means the regression cause is identified and a validated change or follow-up is recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, python
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.