dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 2 Regressions on 7/21/2026 2:43:27 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 | ubuntu 22.04
Queue | ViperUbuntu
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
### Regressions in DemoBenchmarks.OneBodyConstraintBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [OneBodyLinearMotor - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'DemoBenchmarks.OneBodyConstraintBenchmarks*'
```
### DemoBenchmarks.OneBodyConstraintBenchmarks.OneBodyLinearMotor
#### 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 | ubuntu 22.04
Queue | ViperUbuntu
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
### Regressions in DemoBenchmarks.TwoBodyConstraintBenchmarks
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [CenterDistanceConstraint - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'DemoBenchmarks.TwoBodyConstraintBenchmarks*'
```
### DemoBenchmarks.TwoBodyConstraintBenchmarks.CenterDistanceConstraint
#### 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/OneBodyConstraintBenchmarks.cs and TwoBodyConstraintBenchmarks.cs at the referenced benchmark lines, then run the provided benchmarks_ci.py filters on Ubuntu 22.04. Compare the results and profiling data with the listed baseline and commit; done means identifying and addressing the cause of both regressions or documenting why they are expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python, ubuntu
- 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