dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 6/25/2026 12:43:10 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 | [9c1fdaea7e4595785db31a5a219f66fb7d2a4ec1](https://github.com/dotnet/runtime/commit/9c1fdaea7e4595785db31a5a219f66fb7d2a4ec1)
Compare | [818cfd5edcda78ac3eb201af392fd301ab9ad46b](https://github.com/dotnet/runtime/commit/818cfd5edcda78ac3eb201af392fd301ab9ad46b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/9c1fdaea7e4595785db31a5a219f66fb7d2a4ec1...818cfd5edcda78ac3eb201af392fd301ab9ad46b)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Numerics.Tests.Perf_Vector4
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [AbsBenchmark - 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_Vector4*'
```
### System.Numerics.Tests.Perf_Vector4.AbsBenchmark
#### 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 dotnet/performance/src/benchmarks/micro/libraries/System.Numerics.Vectors/Perf_Vector4.cs, especially lines 71-72, and review the linked baseline and compare commits. Run the documented benchmarks_ci.py command with the System.Numerics.Tests.Perf_Vector4 filter, then use the linked report and graph to confirm the wasm improvement. Done requires identifying and validating the cause of the performance change.
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