dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Regression on 8/5/2026 6:23:30 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 | [f107b2325cccfd453f9bf46013159f4704ea56c2](https://github.com/dotnet/runtime/commit/f107b2325cccfd453f9bf46013159f4704ea56c2)
Compare | [b6caa7d9ec9b346b2b09a31ab3fccfe7d049b723](https://github.com/dotnet/runtime/commit/b6caa7d9ec9b346b2b09a31ab3fccfe7d049b723)
Diff | [Diff](https://github.com/dotnet/runtime/compare/f107b2325cccfd453f9bf46013159f4704ea56c2...b6caa7d9ec9b346b2b09a31ab3fccfe7d049b723)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Regressions in PerfLabTests.CastingPerf
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [CheckListIsVariantGenericInterface - 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.CastingPerf*'
```
### PerfLabTests.CastingPerf.CheckListIsVariantGenericInterface
#### 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 in the dotnet/performance benchmark source at src/benchmarks/micro/runtime/perflab/CastingPerf.cs#L407-L412 and run the provided benchmarks_ci.py command for PerfLabTests.CastingPerf. Compare the reported baseline and test results with the linked report and commits. Done means the performance change is explained and the regression is resolved or documented with supporting measurements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100