dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 6/6/2026 4:52: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 | [503cdd143baa519977f4e5f8cc7449fcbfc50c7b](https://github.com/dotnet/runtime/commit/503cdd143baa519977f4e5f8cc7449fcbfc50c7b)
Compare | [10aeb7b7b598aefe7199a065e65316dcf8350815](https://github.com/dotnet/runtime/commit/10aeb7b7b598aefe7199a065e65316dcf8350815)
Diff | [Diff](https://github.com/dotnet/runtime/compare/503cdd143baa519977f4e5f8cc7449fcbfc50c7b...10aeb7b7b598aefe7199a065e65316dcf8350815)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ZeroBenchmark - 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>.ZeroBenchmark
#### 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 System.Numerics.Tests.Perf_VectorOf.ZeroBenchmark source at src/benchmarks/micro/libraries/System.Numerics.Vectors/Perf_VectorOfT.cs#L38-L39 and review the linked test report and IR data. Reproduce the benchmark with benchmarks_ci.py using the documented filter, then determine whether the reported wasm AOT improvement is actionable and provide a verified explanation or follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, 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