dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Improvement on 7/19/2026 5:54:44 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [2515f972d25ec6ab5868f696273bd02a6275e273](https://github.com/dotnet/runtime/commit/2515f972d25ec6ab5868f696273bd02a6275e273)
Compare | [f43516f45fff5920eabd11753bd5f1803cfacd0c](https://github.com/dotnet/runtime/commit/f43516f45fff5920eabd11753bd5f1803cfacd0c)
Diff | [Diff](https://github.com/dotnet/runtime/compare/2515f972d25ec6ab5868f696273bd02a6275e273...f43516f45fff5920eabd11753bd5f1803cfacd0c)
Configs | CompilationMode:tiered, RunKind:micro
### Improvements in System.Numerics.Tensors.Tests.Perf_NumberTensorPrimitives<Double>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Divide_Vector - 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
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Numerics.Tensors.Tests.Perf_NumberTensorPrimitives*'
```
### System.Numerics.Tensors.Tests.Perf_NumberTensorPrimitives<Double>.Divide_Vector(BufferLength: 3079)
#### 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.Numerics.Tensors/Perf_NumberTensorPrimitives.cs, especially Divide_Vector, and run the provided benchmarks_ci.py command. Compare the x86 Windows result with the linked report and runtime commits; done means the reported performance change is understood and any required follow-up is validated.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100