dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/arm64: 2 Improvements on 7/20/2026 8:16:56 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 | [630a7009ba484fe96b8f0b81e2f4cc0bb6827903](https://github.com/dotnet/runtime/commit/630a7009ba484fe96b8f0b81e2f4cc0bb6827903)
Compare | [4d9d5a153993dbeb30910ece8ad346985c55d85d](https://github.com/dotnet/runtime/commit/4d9d5a153993dbeb30910ece8ad346985c55d85d)
Diff | [Diff](https://github.com/dotnet/runtime/compare/630a7009ba484fe96b8f0b81e2f4cc0bb6827903...4d9d5a153993dbeb30910ece8ad346985c55d85d)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Tests.Perf_Boolean
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Parse - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [TryParse - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config 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 'System.Tests.Perf_Boolean*'
```
### System.Tests.Perf_Boolean.Parse(value: " True ")
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Tests.Perf_Boolean.TryParse(value: " True ")
#### 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 benchmark source at src/benchmarks/micro/libraries/System.Runtime/Perf.Boolean.cs and inspect the Parse and TryParse entries in the performance report. Run the provided benchmarks_ci.py command, then determine whether the reported ARM64 improvements need investigation; the issue does not define a requested change or completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100