dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 1 Improvement on 7/11/2026 1:48:32 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 | [1b945942604aa94b4717243b6d301a17b7ae41f1](https://github.com/dotnet/runtime/commit/1b945942604aa94b4717243b6d301a17b7ae41f1)
Compare | [7db43828cc273aa164f2247744a43f70555f780f](https://github.com/dotnet/runtime/commit/7db43828cc273aa164f2247744a43f70555f780f)
Diff | [Diff](https://github.com/dotnet/runtime/compare/1b945942604aa94b4717243b6d301a17b7ae41f1...7db43828cc273aa164f2247744a43f70555f780f)
Configs | CompilationMode:tiered, R2RType:r2r_interpreter, RunKind:micro
### Improvements in MicroBenchmarks.Serializers.Json_ToStream<Location>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SystemTextJson_Reflection_ - Duration of single invocation]()
- [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 'MicroBenchmarks.Serializers.Json_ToStream*'
```
### MicroBenchmarks.Serializers.Json_ToStream<Location>.SystemTextJson_Reflection_
#### 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 profiling and benchmarking workflow docs linked in the issue, then run the benchmarks_ci.py command with the MicroBenchmarks.Serializers.Json_ToStream filter. Inspect the linked test report and compare the ARM64 baseline and test results to determine whether the improvement is reproducible and actionable. Done means the performance change is explained and validated with the benchmark.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100