dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 7/13/2026 2:43:38 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 | [0e7b627c152a3c1885d1db498d81d01de55a3391](https://github.com/dotnet/runtime/commit/0e7b627c152a3c1885d1db498d81d01de55a3391)
Compare | [8df98c4d2d17bcba98193afa9ae2e72908921f86](https://github.com/dotnet/runtime/commit/8df98c4d2d17bcba98193afa9ae2e72908921f86)
Diff | [Diff](https://github.com/dotnet/runtime/compare/0e7b627c152a3c1885d1db498d81d01de55a3391...8df98c4d2d17bcba98193afa9ae2e72908921f86)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Numerics.Tensors.Tests.Perf_FloatingPointTensorPrimitives<Single>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Sigmoid - 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<Single>.Sigmoid(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 in performance/src/benchmarks/micro/libraries/System.Numerics.Tensors/Perf_FloatingPointTensorPrimitives.cs, then review the linked benchmark and profiling workflow documents. Rerun the supplied benchmarks_ci.py command for the Sigmoid case and compare the reported baseline and test results. Done means identifying whether the improvement is reproducible and what follow-up, if any, is warranted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, 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