dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 8/25/2026 11:54:37 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 | [6d57017f1cbf04efa931389d38ca4755e4da8add](https://github.com/dotnet/runtime/commit/6d57017f1cbf04efa931389d38ca4755e4da8add)
Compare | [519e88bf80b5d39bc2c4e788a025a499136a1661](https://github.com/dotnet/runtime/commit/519e88bf80b5d39bc2c4e788a025a499136a1661)
Diff | [Diff](https://github.com/dotnet/runtime/compare/6d57017f1cbf04efa931389d38ca4755e4da8add...519e88bf80b5d39bc2c4e788a025a499136a1661)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Numerics.Tests.Perf_VectorOf<Int32>
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ExclusiveOrOperatorBenchmark - 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_VectorOf*'
```
### System.Numerics.Tests.Perf_VectorOf<Int32>.ExclusiveOrOperatorBenchmark
#### 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.Vectors/Perf_VectorOfT.cs at lines 62-63, then compare the Baseline and Compare commits. Run the documented benchmarks_ci.py command for System.Numerics.Tests.Perf_VectorOf and inspect the linked test report. Done means explaining whether the reported WebAssembly improvement is expected and identifying any follow-up needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux, ubuntu, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100