dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Improvement on 7/19/2026 9:49:55 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 | [c536338d89a6ccc0bcbca46e44e3343d990e06aa](https://github.com/dotnet/runtime/commit/c536338d89a6ccc0bcbca46e44e3343d990e06aa)
Compare | [563abf220847ed66cab58f0d7d166cb264874f40](https://github.com/dotnet/runtime/commit/563abf220847ed66cab58f0d7d166cb264874f40)
Diff | [Diff](https://github.com/dotnet/runtime/compare/c536338d89a6ccc0bcbca46e44e3343d990e06aa...563abf220847ed66cab58f0d7d166cb264874f40)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in PerfLabTests.LowLevelPerf
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [StaticDelegate - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [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 'PerfLabTests.LowLevelPerf*'
```
### PerfLabTests.LowLevelPerf.StaticDelegate
#### 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
The benchmark source is performance/src/benchmarks/micro/runtime/perflab/LowLevelPerf.cs, around lines 283-290. Start by running the provided benchmarks_ci.py command with the PerfLabTests.LowLevelPerf filter and compare the Windows/x86 result with the linked baseline and compare commits. Use the linked benchmarking and profiling workflow docs; done means determining whether the StaticDelegate improvement needs follow-up or only triage.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100