dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 6/17/2026 12:54:02 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 | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [581acb2f5497286af1c2554d68c04312591160ab](https://github.com/dotnet/runtime/commit/581acb2f5497286af1c2554d68c04312591160ab)
Compare | [1af2b9fda524303a30c5d14ac47bbf5510e06102](https://github.com/dotnet/runtime/commit/1af2b9fda524303a30c5d14ac47bbf5510e06102)
Diff | [Diff](https://github.com/dotnet/runtime/compare/581acb2f5497286af1c2554d68c04312591160ab...1af2b9fda524303a30c5d14ac47bbf5510e06102)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Regressions in PerfLabTests.EnumPerf
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ObjectGetTypeNoBoxing - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'PerfLabTests.EnumPerf*'
```
### PerfLabTests.EnumPerf.ObjectGetTypeNoBoxing
#### 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 PerfLabTests.EnumPerf.ObjectGetTypeNoBoxing entry in src/benchmarks/micro/runtime/perflab/EnumPerf.cs and reproduce it with the benchmarks_ci.py command. Compare the baseline and comparison commits, then use the linked test report and performance graph to investigate the regression. Done means the regression is explained and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ubuntu, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100