dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 1 Improvement on 6/23/2026 8:41:58 PM +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 | [e3ecd30e4d6bfeedec6b4730c8ef87951cfe1f17](https://github.com/dotnet/runtime/commit/e3ecd30e4d6bfeedec6b4730c8ef87951cfe1f17)
Compare | [feb1fe23e41b7af2401edbd4230bf11dcb9cfc96](https://github.com/dotnet/runtime/commit/feb1fe23e41b7af2401edbd4230bf11dcb9cfc96)
Diff | [Diff](https://github.com/dotnet/runtime/compare/e3ecd30e4d6bfeedec6b4730c8ef87951cfe1f17...feb1fe23e41b7af2401edbd4230bf11dcb9cfc96)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in ByteMark
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [BenchNeuralJagged - 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 'ByteMark*'
```
### ByteMark.BenchNeuralJagged
#### 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 ByteMark.cs benchmark source around lines 501-510 and the linked Test Report for BenchNeuralJagged. Reproduce the result with the documented benchmarks_ci.py command and compare the ARM64 AzureLinux data; the issue does not specify a code change or acceptance condition, so the next action requires triage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, linux
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100