dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 8/21/2026 7:05:07 PM +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 | [76c60b960a2daa412c44a5061abf66f3286f6a92](https://github.com/dotnet/runtime/commit/76c60b960a2daa412c44a5061abf66f3286f6a92)
Compare | [58a829968e8d2624cbcb4e2ce7f1bb01cb9f652b](https://github.com/dotnet/runtime/commit/58a829968e8d2624cbcb4e2ce7f1bb01cb9f652b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/76c60b960a2daa412c44a5061abf66f3286f6a92...58a829968e8d2624cbcb4e2ce7f1bb01cb9f652b)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Reflection.Invoke
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Field_Set_class - 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 'System.Reflection.Invoke*'
```
### System.Reflection.Invoke.Field_Set_class
#### 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 System.Reflection.Invoke benchmark in performance/src/benchmarks/micro/runtime/System.Reflection/Invoke.cs, lines 448-455, and reproduce it with the provided benchmarks_ci.py command. Compare the listed baseline and test commits, then use the profiling workflow to identify the regression; done means the benchmark no longer shows the reported slowdown.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100