dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/2/2026 1:46:10 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 | [1645260ffcbdc651dd3c0938be593cdb5bcec492](https://github.com/dotnet/runtime/commit/1645260ffcbdc651dd3c0938be593cdb5bcec492)
Compare | [79efd2de59f086171fd811d7375241616c43b890](https://github.com/dotnet/runtime/commit/79efd2de59f086171fd811d7375241616c43b890)
Diff | [Diff](https://github.com/dotnet/runtime/compare/1645260ffcbdc651dd3c0938be593cdb5bcec492...79efd2de59f086171fd811d7375241616c43b890)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Runtime.Intrinsics.Tests.Perf_Vector128Of<Int16>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [EqualityOperatorBenchmark - 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<Int16>.EqualityOperatorBenchmark
#### 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, Perf_Vector128OfT.cs lines 55–56, and the benchmarking workflow documentation. Run the provided benchmarks_ci.py command, then inspect the linked history, graph, and test report to determine whether the reported WebAssembly improvement is actionable. The issue provides no requested code change or acceptance condition, so completion would require triage first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100