dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 7/15/2026 9:06:05 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 | [c98e79e96affb873c827e32c779a68b1368cc480](https://github.com/dotnet/sdk/commit/c98e79e96affb873c827e32c779a68b1368cc480)
Compare | [ecc427bc7d7b4ee32b943f71196ab377f67c1105](https://github.com/dotnet/sdk/commit/ecc427bc7d7b4ee32b943f71196ab377f67c1105)
Diff | [Diff](https://github.com/dotnet/sdk/compare/c98e79e96affb873c827e32c779a68b1368cc480...ecc427bc7d7b4ee32b943f71196ab377f67c1105)
Configs | CompilationMode:tiered, RunKind:scenarios
### Improvements 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 benchmarking workflow documentation and reproduce the reported Startup - PaintDotNet - FDD Publish scenario using scripts/benchmarks_ci.py with the supplied filter. Compare the baseline and test reports, then use the profiling workflow and linked ETL, histogram, or JIT data to investigate. Done should mean the reported performance issue is understood and a measurable result is documented.
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
- 28/100