dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 3 Regressions on 6/15/2026 9:08:26 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 | [6e2abd36c0e9d4781a3c1534677d92dbd38a41a8](https://github.com/dotnet/sdk/commit/6e2abd36c0e9d4781a3c1534677d92dbd38a41a8)
Compare | [06787fc66d5364230924d00f2c5c251aeb7a31cd](https://github.com/dotnet/sdk/commit/06787fc66d5364230924d00f2c5c251aeb7a31cd)
Diff | [Diff](https://github.com/dotnet/sdk/compare/6e2abd36c0e9d4781a3c1534677d92dbd38a41a8...06787fc66d5364230924d00f2c5c251aeb7a31cd)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Regressions in DemoBenchmarks.TwoBodyConstraintBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [LinearAxisServo - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [Contact4Nonconvex - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [DistanceServo - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
![graph]()
![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.LinearAxisServo
#### ETL Files
#### Histogram
#### JIT Disasms
### DemoBenchmarks.TwoBodyConstraintBenchmarks.Contact4Nonconvex
#### ETL Files
#### Histogram
#### JIT Disasms
### 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 the three benchmark entries and source ranges in src/benchmarks/real-world/bepuphysics2/TwoBodyConstraintBenchmarks.cs, then run the documented benchmarks_ci.py command for DemoBenchmarks.TwoBodyConstraintBenchmarks. Compare the baseline and test commits and inspect the linked test report and graphs. Done means the reported Windows/x64 regressions are explained and the affected benchmark results no longer regress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100