dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/2/2026 11:04:49 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 | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [a2f953fe266dc72602436e77614a9e10f60a7128](https://github.com/dotnet/runtime/commit/a2f953fe266dc72602436e77614a9e10f60a7128)
Compare | [abcd6eb3137ac133ef7f73eae95e7928160386c9](https://github.com/dotnet/runtime/commit/abcd6eb3137ac133ef7f73eae95e7928160386c9)
Diff | [Diff](https://github.com/dotnet/runtime/compare/a2f953fe266dc72602436e77614a9e10f60a7128...abcd6eb3137ac133ef7f73eae95e7928160386c9)
Configs | CompilationMode:wasm, RunKind:micro, RuntimeType:coreclr
### Improvements in PerfLabTests.CastingPerf2.CastingPerf
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ScalarValueTypeObj - 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.CastingPerf2.CastingPerf*'
```
### PerfLabTests.CastingPerf2.CastingPerf.ScalarValueTypeObj
#### 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 CastingPerf2.cs benchmark and the perf report for ScalarValueTypeObj, then rerun the provided benchmarks_ci.py command using the documented workflow. Compare the baseline and test commits and investigate whether the reported improvement is reproducible; the result should establish the cause or provide a clear triage outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100