dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Improvement on 9/3/2026 2:35:28 PM +00:00
- 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 | [147c024e64965dd98d68ed8419e4f5320852e8ca](https://github.com/dotnet/sdk/commit/147c024e64965dd98d68ed8419e4f5320852e8ca)
Compare | [1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d](https://github.com/dotnet/sdk/commit/1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d)
Diff | [Diff](https://github.com/dotnet/sdk/compare/147c024e64965dd98d68ed8419e4f5320852e8ca...1fee94ef34a9c6e2e4cf4199d9a546ef8a2a927d)
Configs | CompilationMode:tiered, RunKind:sdk_scenarios
### Improvements in SDK New Console
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SDK New Console - Process Time]()
- [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 'SDK New Console*'
```
### SDK New 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 linked SDK New Console benchmark report and the benchmarking workflow in docs/benchmarking-workflow-dotnet-runtime.md. Run the supplied benchmarks_ci.py command and compare the baseline and test results on Windows x86. Done means identifying and documenting the cause or actionable change behind the reported performance difference, with the benchmark result reproduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100