dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Improvement on 7/21/2026 2:38:45 PM +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 | [7e07d48faae88ae9068a6afc91e7524b2112c0e7](https://github.com/dotnet/sdk/commit/7e07d48faae88ae9068a6afc91e7524b2112c0e7)
Compare | [d2b524965e50619e8db62ed35943981830e1008d](https://github.com/dotnet/sdk/commit/d2b524965e50619e8db62ed35943981830e1008d)
Diff | [Diff](https://github.com/dotnet/sdk/compare/7e07d48faae88ae9068a6afc91e7524b2112c0e7...d2b524965e50619e8db62ed35943981830e1008d)
Configs | CompilationMode:tiered, RunKind:bepuphysics
### Improvements 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]()
![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
### 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 at lines 252-267 and review the linked LinearAxisServo benchmark and test report. Run the provided benchmarks_ci.py command, then compare the baseline and test results and inspect the linked history or report data. Done means identifying and validating the cause of the reported performance change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100