dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 9/8/2026 7:05:26 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 | [2120018b13c80b3bfff680dcfa93bc2e668664cc](https://github.com/dotnet/runtime/commit/2120018b13c80b3bfff680dcfa93bc2e668664cc)
Compare | [fd066085aedc77cee69e3169225a24457e63a714](https://github.com/dotnet/runtime/commit/fd066085aedc77cee69e3169225a24457e63a714)
Diff | [Diff](https://github.com/dotnet/runtime/compare/2120018b13c80b3bfff680dcfa93bc2e668664cc...fd066085aedc77cee69e3169225a24457e63a714)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Numerics.Tensors.Tests.Perf_FloatingPointTensorPrimitives<Double>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Log - 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.Tensors.Tests.Perf_FloatingPointTensorPrimitives*'
```
### System.Numerics.Tensors.Tests.Perf_FloatingPointTensorPrimitives<Double>.Log(BufferLength: 128)
#### 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 linked benchmark source in src/benchmarks/micro/libraries/System.Numerics.Tensors/Perf_FloatingPointTensorPrimitives.cs and review the Log(BufferLength: 128) result. Run the provided benchmarks_ci.py command to reproduce the WebAssembly measurement; the issue does not define a code change or completion condition, so triage must establish what should be done.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100