dotnet / dotnet/perf-autofiling-issues

[Perf] Windows/x86: 2 Improvements on 6/3/2026 8:45:46 AM +00:00

Open
#74,028 1 comment 0 reactions 0 assignees View on GitHub
arch-x86 branch-11.0 compilationmode-tiered kind-sdk_scenarios Noise os-windows perf-improvement runkind-sdk_scenarios untriaged
Dominant language
No language data
Stars
10
Forks
8
PR merge metrics
PR metrics pending

Description

### Run Information

Name | Value
-- | --
Architecture | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [1616fce88662817fb8b76911fb188b56650859a0](https://github.com/dotnet/sdk/commit/1616fce88662817fb8b76911fb188b56650859a0)
Compare | [953380f224e6f6ee72662fdee8b27900adbb29c2](https://github.com/dotnet/sdk/commit/953380f224e6f6ee72662fdee8b27900adbb29c2)
Diff | [Diff](https://github.com/dotnet/sdk/compare/1616fce88662817fb8b76911fb188b56650859a0...953380f224e6f6ee72662fdee8b27900adbb29c2)
Configs | CompilationMode:tiered, RunKind:sdk_scenarios

### Improvements in SDK MSTest Test Project (.NET Core) Template Clean Build

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

  • [SDK MSTest Test Project - Process Time]()
  • [ADX - Test Multi Config Graph]()
| 3187.11 ms | 3116.79 ms | 0.98 | 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 'SDK MSTest Test Project (.NET Core) Template Clean Build*'
```

### SDK MSTest Test Project (.NET Core) Template Clean Build

#### 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 | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [1616fce88662817fb8b76911fb188b56650859a0](https://github.com/dotnet/sdk/commit/1616fce88662817fb8b76911fb188b56650859a0)
Compare | [953380f224e6f6ee72662fdee8b27900adbb29c2](https://github.com/dotnet/sdk/commit/953380f224e6f6ee72662fdee8b27900adbb29c2)
Diff | [Diff](https://github.com/dotnet/sdk/compare/1616fce88662817fb8b76911fb188b56650859a0...953380f224e6f6ee72662fdee8b27900adbb29c2)
Configs | CompilationMode:tiered, RunKind:sdk_scenarios

### Improvements in Inner Loop Console

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

  • [Inner Loop Console - Generic Startup Diff]()
  • [ADX - Test Multi Config Graph]()
| 202.53 ms | 194.22 ms | 0.96 | 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 'Inner Loop Console*'
```

### Inner Loop Console

#### 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 supplied benchmarking workflow documentation and reproduce the two named scenarios using the provided benchmarks_ci.py commands. Compare the Windows x86 results and linked reports for SDK MSTest Test Project (.NET Core) Template Clean Build and Inner Loop Console. The issue does not identify a source file or define a corrective change, so completion would require triage to determine what, if anything, should be changed.

Written by the indexing model from the issue text.

Assessment

Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.