dotnet / dotnet/perf-autofiling-issues

[Perf] Linux/x64: 2 Improvements on 6/25/2026 8:43:50 AM +00:00

Open
#75,956 1 comment 0 reactions 0 assignees View on GitHub
arch-wasm arch-x64 branch-refs/heads/main compilationmode-wasm kind-micro Look Again os-linux perf-improvement runkind-micro untriaged
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 | [cd27dcec16016aa54be6a09962d1b509150cf99b](https://github.com/dotnet/runtime/commit/cd27dcec16016aa54be6a09962d1b509150cf99b)
Compare | [d6c7fb69f882c3ffd49de58dd009330e2a915402](https://github.com/dotnet/runtime/commit/d6c7fb69f882c3ffd49de58dd009330e2a915402)
Diff | [Diff](https://github.com/dotnet/runtime/compare/cd27dcec16016aa54be6a09962d1b509150cf99b...d6c7fb69f882c3ffd49de58dd009330e2a915402)
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
-- | -- | -- | -- | -- | -- | -- | -- | --
|

  • [EqualsStaticBenchmark - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 12.25 ns | 10.61 ns | 0.87 | 0.49 | False | | |

![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>.EqualsStaticBenchmark

#### 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)

---

### Run Information

Name | Value
-- | --
Architecture | x64
OS | ubuntu 22.04
Queue | ViperUbuntu
Baseline | [cd27dcec16016aa54be6a09962d1b509150cf99b](https://github.com/dotnet/runtime/commit/cd27dcec16016aa54be6a09962d1b509150cf99b)
Compare | [d6c7fb69f882c3ffd49de58dd009330e2a915402](https://github.com/dotnet/runtime/commit/d6c7fb69f882c3ffd49de58dd009330e2a915402)
Diff | [Diff](https://github.com/dotnet/runtime/compare/cd27dcec16016aa54be6a09962d1b509150cf99b...d6c7fb69f882c3ffd49de58dd009330e2a915402)
Configs | CompilationMode:wasm, RunKind:micro

### Improvements in System.Memory.MemoryMarshal<Int32>

Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|

  • [AsBytes - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 19.17 ns | 17.06 ns | 0.89 | 0.30 | False | | |

![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.Memory.MemoryMarshal*'
```

### System.Memory.MemoryMarshal<Int32>.AsBytes

#### 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 two linked benchmark source files, Perf_VectorOfT.cs and MemoryMarshal.cs, and reproduce both filters with the provided benchmarks_ci.py commands. Compare the reported baseline and test timings, then inspect the linked test reports and profiling workflow docs. Done means the improvement is explained or validated and any necessary follow-up is identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python, wasm
Domain
performance, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.