dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 1 Improvement on 6/16/2026 1:50:56 AM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | arm64
OS | azurelinux 3.0
Queue | CobaltAzureLinux
Baseline | [fd3a4f4683bb4adda7785506b9a8fc5c2607b422](https://github.com/dotnet/runtime/commit/fd3a4f4683bb4adda7785506b9a8fc5c2607b422)
Compare | [98d5787a726f050c592e7c126c6ab62b1954288c](https://github.com/dotnet/runtime/commit/98d5787a726f050c592e7c126c6ab62b1954288c)
Diff | [Diff](https://github.com/dotnet/runtime/compare/fd3a4f4683bb4adda7785506b9a8fc5c2607b422...98d5787a726f050c592e7c126c6ab62b1954288c)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in SIMD.ConsoleMandel
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [VectorDoubleSinglethreadADT - 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 'SIMD.ConsoleMandel*'
```
### SIMD.ConsoleMandel.VectorDoubleSinglethreadADT
#### 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 SIMD.ConsoleMandel benchmark source at src/benchmarks/micro/runtime/SIMD/ConsoleMandel/ConsoleMandel.cs#L79-L81 and the linked test report. Run the documented benchmarks_ci.py command, then compare the arm64 AzureLinux result with the baseline and investigate the reported change. Done requires a confirmed explanation or an agreed follow-up, but the issue does not specify a code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, linux, python
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100