dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 6/17/2026 6:19:41 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 | [1af2b9fda524303a30c5d14ac47bbf5510e06102](https://github.com/dotnet/runtime/commit/1af2b9fda524303a30c5d14ac47bbf5510e06102)
Compare | [d72d2fcf29301c5f9fe2c7188c90df93b0730989](https://github.com/dotnet/runtime/commit/d72d2fcf29301c5f9fe2c7188c90df93b0730989)
Diff | [Diff](https://github.com/dotnet/runtime/compare/1af2b9fda524303a30c5d14ac47bbf5510e06102...d72d2fcf29301c5f9fe2c7188c90df93b0730989)
Configs | AOT:true, 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
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [DivideByScalarBenchmark - 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.DivideByScalarBenchmark
#### 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_Vector4.cs at lines 93-94 and run the provided benchmarks_ci.py command. Compare the baseline and test reports for DivideByScalarBenchmark to determine whether the improvement is reproducible; the issue provides no prescribed code change or completion criterion.
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
- 25/100