dotnet / dotnet/perf-autofiling-issues

[Perf] Windows/x64: 2 Improvements on 9/5/2026 11:04:57 AM +00:00

Open
#78,991 1 comment 0 reactions 0 assignees View on GitHub
arch-x64 branch-11.0 compilationmode-tiered kind-bepuphysics Look Again os-windows perf-improvement runkind-bepuphysics runtime-coreclr untriaged
Dominant language
No language data
Stars
10
Forks
8
PR merge metrics
PR metrics pending

Description

### Run Information

Name | Value
-- | --
Architecture | x64
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [f8a811758057986566da27d06d8f03a7e5e226bf](https://github.com/dotnet/sdk/commit/f8a811758057986566da27d06d8f03a7e5e226bf)
Compare | [c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da](https://github.com/dotnet/sdk/commit/c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da)
Diff | [Diff](https://github.com/dotnet/sdk/compare/f8a811758057986566da27d06d8f03a7e5e226bf...c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da)
Configs | CompilationMode:tiered, RunKind:bepuphysics

### Improvements in DemoBenchmarks.GatherScatterBenchmarks

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

  • [GatherState - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 24.30 μs | 21.21 μs | 0.87 | 0.00 | True | | |

![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 'DemoBenchmarks.GatherScatterBenchmarks*'
```

### DemoBenchmarks.GatherScatterBenchmarks.GatherState

#### 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [f8a811758057986566da27d06d8f03a7e5e226bf](https://github.com/dotnet/sdk/commit/f8a811758057986566da27d06d8f03a7e5e226bf)
Compare | [c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da](https://github.com/dotnet/sdk/commit/c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da)
Diff | [Diff](https://github.com/dotnet/sdk/compare/f8a811758057986566da27d06d8f03a7e5e226bf...c9b72963eb22ce3f8eb2ad8ebedf9ecef57615da)
Configs | CompilationMode:tiered, RunKind:bepuphysics

### Improvements in DemoBenchmarks.TwoBodyConstraintBenchmarks

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

  • [Contact4Nonconvex - Duration of single invocation]()
  • 📝 - [Benchmark Source]()
  • [ADX - Test Multi Config Graph]()
| 546.74 μs | 484.97 μs | 0.89 | 0.00 | True | | |

![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 'DemoBenchmarks.TwoBodyConstraintBenchmarks*'
```

### DemoBenchmarks.TwoBodyConstraintBenchmarks.Contact4Nonconvex

#### 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 mentioned benchmark sources, src/benchmarks/real-world/bepuphysics2/GatherScatterBenchmarks.cs and TwoBodyConstraintBenchmarks.cs, then run the provided benchmarks_ci.py commands. Inspect the linked test reports and baseline/compare data. Completion criteria are not stated beyond reporting two performance improvements, so clarify the desired change before coding.

Written by the indexing model from the issue text.

Assessment

Domain
performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.