dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/10/2026 5:40:28 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 | [9904b9343c89c898fea3a9dfa68a6aba7fa8f3c1](https://github.com/dotnet/runtime/commit/9904b9343c89c898fea3a9dfa68a6aba7fa8f3c1)
Compare | [ab094c18ba7f4a96d145afd8b34f965c5c3ef31d](https://github.com/dotnet/runtime/commit/ab094c18ba7f4a96d145afd8b34f965c5c3ef31d)
Diff | [Diff](https://github.com/dotnet/runtime/compare/9904b9343c89c898fea3a9dfa68a6aba7fa8f3c1...ab094c18ba7f4a96d145afd8b34f965c5c3ef31d)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Runtime.Intrinsics.Tests.Perf_Vector128
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ConvertDoubleToULongBenchmark - 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.Runtime.Intrinsics.Tests.Perf_Vector128*'
```
### System.Runtime.Intrinsics.Tests.Perf_Vector128.ConvertDoubleToULongBenchmark
#### 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 in performance/src/benchmarks/micro/libraries/System.Runtime.Intrinsics/Perf_Vector128.cs at lines 54-55, then read the benchmarking workflow documentation and reproduce the System.Runtime.Intrinsics.Tests.Perf_Vector128 run. Compare the baseline and test results for ConvertDoubleToULongBenchmark and determine whether the reported improvement is expected; done means the performance change is explained and any needed follow-up is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, ubuntu, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100