dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 6/17/2026 9:03:31 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 | [f0130b9b5627afa36f53d339e6788a4a1783d08f](https://github.com/dotnet/sdk/commit/f0130b9b5627afa36f53d339e6788a4a1783d08f)
Compare | [a50a8baa52210e32fb688a6cb7f59e40b79ff830](https://github.com/dotnet/sdk/commit/a50a8baa52210e32fb688a6cb7f59e40b79ff830)
Diff | [Diff](https://github.com/dotnet/sdk/compare/f0130b9b5627afa36f53d339e6788a4a1783d08f...a50a8baa52210e32fb688a6cb7f59e40b79ff830)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Regressions in DemoBenchmarks.TwoBodyConstraintBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [DistanceServo - 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.TwoBodyConstraintBenchmarks*'
```
### DemoBenchmarks.TwoBodyConstraintBenchmarks.DistanceServo
#### 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/TwoBodyConstraintBenchmarks.cs, then run the provided benchmarks_ci.py command for the DistanceServo benchmark. Compare the baseline and compare commits and use the linked benchmark and test reports to investigate the regression; done requires a reproducible result and a documented cause or resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100