dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 5/4/2026 1:43:36 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 | [b6b7d929d43ec150af954e2e963ccb9b024274ba](https://github.com/dotnet/runtime/commit/b6b7d929d43ec150af954e2e963ccb9b024274ba)
Compare | [5761661dc931d1f14531b8c91bf88344d2a1dc09](https://github.com/dotnet/runtime/commit/5761661dc931d1f14531b8c91bf88344d2a1dc09)
Diff | [Diff](https://github.com/dotnet/runtime/compare/b6b7d929d43ec150af954e2e963ccb9b024274ba...5761661dc931d1f14531b8c91bf88344d2a1dc09)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Numerics.Tests.Perf_VectorOf<Single>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ConditionalSelectBenchmark - 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.Numerics.Tests.Perf_VectorOf*'
```
### System.Numerics.Tests.Perf_VectorOf<Single>.ConditionalSelectBenchmark
#### 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 src/benchmarks/micro/libraries/System.Numerics.Vectors/Perf_VectorOfT.cs at lines 95-96, then run the documented benchmarks_ci.py command for the ConditionalSelectBenchmark. Compare the listed baseline and test commits and use the linked report to determine whether the wasm AOT improvement is reproducible and what change explains it; done means the result is understood and any required follow-up is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100