dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 6/19/2026 6:38:08 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 | [ee2a8a9df2f6fc43c85e2aec1c8cae2e22d97e12](https://github.com/dotnet/runtime/commit/ee2a8a9df2f6fc43c85e2aec1c8cae2e22d97e12)
Compare | [18696adecd2e6e6528ba3d543c97b0013b961aa6](https://github.com/dotnet/runtime/commit/18696adecd2e6e6528ba3d543c97b0013b961aa6)
Diff | [Diff](https://github.com/dotnet/runtime/compare/ee2a8a9df2f6fc43c85e2aec1c8cae2e22d97e12...18696adecd2e6e6528ba3d543c97b0013b961aa6)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Runtime.Intrinsics.Tests.Perf_Vector128Of<UInt64>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [SquareRootBenchmark - 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_Vector128Of*'
```
### System.Runtime.Intrinsics.Tests.Perf_Vector128Of<UInt64>.SquareRootBenchmark
#### 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_Vector128OfT.cs around lines 160-161, then read the benchmarking workflow documentation. Run the supplied benchmarks_ci.py command and inspect the baseline/compare reports for the WASM AOT configuration. Done means identifying a reproducible, actionable performance change, but the issue does not specify one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100