dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 6/18/2026 9:53:01 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 | [a17debec450d73f9d84e68ca44f63b217f5db49f](https://github.com/dotnet/runtime/commit/a17debec450d73f9d84e68ca44f63b217f5db49f)
Compare | [482f9baca29117c07eb4f9ab5404990746986ce0](https://github.com/dotnet/runtime/commit/482f9baca29117c07eb4f9ab5404990746986ce0)
Diff | [Diff](https://github.com/dotnet/runtime/compare/a17debec450d73f9d84e68ca44f63b217f5db49f...482f9baca29117c07eb4f9ab5404990746986ce0)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ConvertUIntToFloatBenchmark - 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.ConvertUIntToFloatBenchmark
#### 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 benchmark source in dotnet/performance/src/benchmarks/micro/libraries/System.Runtime.Intrinsics/Perf_Vector128.cs at lines 48-49, then review the linked history and test report for ConvertUIntToFloatBenchmark. Reproduce it with the provided benchmarks_ci.py command. Done would require identifying a concrete issue or follow-up change behind the reported performance difference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100