dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 8/28/2026 9:44:12 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 | [bf3289d05dff3962cdccb0e81b5315990e5b1198](https://github.com/dotnet/sdk/commit/bf3289d05dff3962cdccb0e81b5315990e5b1198)
Compare | [100002779ceec649fcfd00c233f673b494130827](https://github.com/dotnet/sdk/commit/100002779ceec649fcfd00c233f673b494130827)
Diff | [Diff](https://github.com/dotnet/sdk/compare/bf3289d05dff3962cdccb0e81b5315990e5b1198...100002779ceec649fcfd00c233f673b494130827)
Configs | CompilationMode:tiered, RunKind:scenarios
### Improvements in Startup - Static VB Console Template - FDD Publish
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Startup - Static VB Console Template - FDD Publish - Time To Main]()
- [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 - Static VB Console Template - FDD Publish*'
```
### Startup - Static VB Console Template - 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 linked benchmark report and run the provided benchmarks_ci.py command for the Static VB Console Template FDD Publish scenario on Windows x64. Compare the baseline and test results and inspect the linked performance data to determine what change, if any, should be made; the issue does not define a concrete fix or completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- visualbasic
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100