dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 8/12/2026 9:11:00 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 | Windows 10.0.22631
Queue | ViperWindows
Baseline | [10d231dd86555cc17a757c800d821ad8e0f459d5](https://github.com/dotnet/sdk/commit/10d231dd86555cc17a757c800d821ad8e0f459d5)
Compare | [64a29867c5c5c8e0babc9e31313cf3b6e50f0193](https://github.com/dotnet/sdk/commit/64a29867c5c5c8e0babc9e31313cf3b6e50f0193)
Diff | [Diff](https://github.com/dotnet/sdk/compare/10d231dd86555cc17a757c800d821ad8e0f459d5...64a29867c5c5c8e0babc9e31313cf3b6e50f0193)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Improvements in DemoBenchmarks.GroupedCollisionTesterBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [CheapCollisionBenchmarks - 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
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'DemoBenchmarks.GroupedCollisionTesterBenchmarks*'
```
### DemoBenchmarks.GroupedCollisionTesterBenchmarks.CheapCollisionBenchmarks
#### 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 src/benchmarks/real-world/bepuphysics2/GroupedCollisionTesterBenchmarks.cs, especially the CheapCollisionBenchmarks source linked in the report. Run the provided benchmarks_ci.py command and compare the reported Windows/x64 results against the baseline and comparison commits. Done means determining whether the measured improvement is actionable and identifying the corresponding repository change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100