dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x64: 1 Regression on 7/3/2026 5:00:33 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 | [bcaa8d44d57494224d443dba7c1dfed381ad5528](https://github.com/dotnet/sdk/commit/bcaa8d44d57494224d443dba7c1dfed381ad5528)
Compare | [fa2f7be0dd4fcfaf582f468bab7da8cb46b8d39d](https://github.com/dotnet/sdk/commit/fa2f7be0dd4fcfaf582f468bab7da8cb46b8d39d)
Diff | [Diff](https://github.com/dotnet/sdk/compare/bcaa8d44d57494224d443dba7c1dfed381ad5528...fa2f7be0dd4fcfaf582f468bab7da8cb46b8d39d)
Configs | CompilationMode:tiered, RunKind:fsharpmicro
### Regressions in MicroBenchmarks.FSharp.Collections+CollectionsBenchmark
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [ArrayRemoveAtEnd - Duration of single invocation]()
- [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 'MicroBenchmarks.FSharp.Collections+CollectionsBenchmark*'
```
### MicroBenchmarks.FSharp.Collections+CollectionsBenchmark.ArrayRemoveAtEnd(Length: 10000)
#### 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 MicroBenchmarks.FSharp.Collections+CollectionsBenchmark.ArrayRemoveAtEnd benchmark and the provided benchmarks_ci.py command, then compare the linked baseline and test commits and inspect the regression report. Use the benchmarking workflow documentation and report links to determine the cause; done means the regression is explained and its resolution or follow-up is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100