dotnet / dotnet/perf-autofiling-issues

[Perf] Linux/arm64: 5 Improvements on 7/21/2026 3:12:56 AM +00:00

Open
#77,104 1 comment 0 reactions 0 assignees View on GitHub
arch-arm64 branch-refs/heads/main compilationmode-tiered kind-micro os-linux perf-improvement runkind-micro runtime-coreclr untriaged
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 | [73a9e0a51ed85481b7f03ca3f2696e020365afd6](https://github.com/dotnet/runtime/commit/73a9e0a51ed85481b7f03ca3f2696e020365afd6)
Compare | [7e3626903d758fab196fa09782a7e198a985bf36](https://github.com/dotnet/runtime/commit/7e3626903d758fab196fa09782a7e198a985bf36)
Diff | [Diff](https://github.com/dotnet/runtime/compare/73a9e0a51ed85481b7f03ca3f2696e020365afd6...7e3626903d758fab196fa09782a7e198a985bf36)
Configs | CompilationMode:tiered, RunKind:micro

### Improvements in Microsoft.AspNetCore.Server.Kestrel.Performance.PipeThroughputBenchmark

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

  • [Parse_ParallelAsync - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 1201.45 ns | 300.07 ns | 0.25 | 0.55 | False | | |
|
  • [Parse_SequentialAsync - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 695.01 ns | 348.21 ns | 0.50 | 0.31 | False | | |
|
  • [Parse_SequentialAsync - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 669.97 ns | 348.59 ns | 0.52 | 0.34 | False | | |
|
  • [Parse_ParallelAsync - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 266.72 ns | 141.89 ns | 0.53 | 0.52 | False | | |
|
  • [Parse_ParallelAsync - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 1.85 μs | 1.07 μs | 0.58 | 0.53 | False | | |

![graph]()
![graph]()
![graph]()
![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 'Microsoft.AspNetCore.Server.Kestrel.Performance.PipeThroughputBenchmark*'
```

### Microsoft.AspNetCore.Server.Kestrel.Performance.PipeThroughputBenchmark.Parse_ParallelAsync(Length: 128, Chunks: 16)

#### ETL Files

#### Histogram

#### JIT Disasms

### Microsoft.AspNetCore.Server.Kestrel.Performance.PipeThroughputBenchmark.Parse_SequentialAsync(Length: 4096, Chunks: 16)

#### ETL Files

#### Histogram

#### JIT Disasms

### Microsoft.AspNetCore.Server.Kestrel.Performance.PipeThroughputBenchmark.Parse_SequentialAsync(Length: 128, Chunks: 16)

#### ETL Files

#### Histogram

#### JIT Disasms

### Microsoft.AspNetCore.Server.Kestrel.Performance.PipeThroughputBenchmark.Parse_ParallelAsync(Length: 128, Chunks: 1)

#### ETL Files

#### Histogram

#### JIT Disasms

### Microsoft.AspNetCore.Server.Kestrel.Performance.PipeThroughputBenchmark.Parse_ParallelAsync(Length: 4096, Chunks: 16)

#### 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 benchmark source at src/benchmarks/micro/libraries/System.IO.Pipelines/PipeThroughputBenchmark.cs, especially the Parse_ParallelAsync and Parse_SequentialAsync methods. Run the documented benchmarks_ci.py command and inspect the linked test report and comparisons; the issue does not define a specific change or acceptance criterion, so the desired outcome requires triage first.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, linux
Domain
backend, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.