dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/7/2026 9:57:17 AM +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 | [9bf3be3ad48e77e97436fa96825cb713a6964389](https://github.com/dotnet/runtime/commit/9bf3be3ad48e77e97436fa96825cb713a6964389)
Compare | [7da460b99b9c7e76b3060ef6da6687a008263ab9](https://github.com/dotnet/runtime/commit/7da460b99b9c7e76b3060ef6da6687a008263ab9)
Diff | [Diff](https://github.com/dotnet/runtime/compare/9bf3be3ad48e77e97436fa96825cb713a6964389...7da460b99b9c7e76b3060ef6da6687a008263ab9)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Numerics.Tests.Perf_VectorConvert
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Narrow_int - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Numerics.Tests.Perf_VectorConvert*'
```
### System.Numerics.Tests.Perf_VectorConvert.Narrow_int
#### 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
Read the benchmark source in performance/src/benchmarks/micro/libraries/System.Numerics.Vectors/Perf_VectorConvert.cs at lines 68-69, then run the provided benchmarks_ci.py command for Perf_VectorConvert. Compare the Narrow_int result with the linked baseline, test report, and runtime commits; done requires a confirmed, actionable explanation or follow-up for the reported performance change.
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