dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 7/1/2026 9:59:07 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [88e2ee68affb2e6e71727630df8833dced0875f4](https://github.com/dotnet/runtime/commit/88e2ee68affb2e6e71727630df8833dced0875f4)
Compare | [2ca5bd514647fe0e961dd237dc9af0004479da6f](https://github.com/dotnet/runtime/commit/2ca5bd514647fe0e961dd237dc9af0004479da6f)
Diff | [Diff](https://github.com/dotnet/runtime/compare/88e2ee68affb2e6e71727630df8833dced0875f4...2ca5bd514647fe0e961dd237dc9af0004479da6f)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Perf_Convert
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [FromHexString - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Perf_Convert*'
```
### System.Perf_Convert.FromHexString
#### 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 System.Perf_Convert.FromHexString history and report, then reproduce it with the benchmarks_ci.py command and the System.Perf_Convert* filter. Compare the baseline and test runs and inspect the referenced profiling or benchmarking workflow docs. The issue does not identify a source file or specify a change, so completion would require triage to establish the intended follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100