dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/2/2026 5:36:12 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 | [c25173808a41517b547a0880a424d64aff9c7e80](https://github.com/dotnet/runtime/commit/c25173808a41517b547a0880a424d64aff9c7e80)
Compare | [75c1187a6c4669f5b35f2e900a659b4a55f352c6](https://github.com/dotnet/runtime/commit/75c1187a6c4669f5b35f2e900a659b4a55f352c6)
Diff | [Diff](https://github.com/dotnet/runtime/compare/c25173808a41517b547a0880a424d64aff9c7e80...75c1187a6c4669f5b35f2e900a659b4a55f352c6)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Runtime.Intrinsics.Tests.Perf_Vector128Of<UInt32>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [MaxBenchmark - 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<UInt32>.MaxBenchmark
#### 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 at src/benchmarks/micro/libraries/System.Runtime.Intrinsics/Perf_Vector128OfT.cs#L145-L146 and reproduce the reported case using the provided benchmarks_ci.py command. Compare the benchmark and report links to understand the wasm result; completion criteria are not specified in the issue and require triage before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100