dotnet / dotnet/perf-autofiling-issues
[Perf] Windows/x86: 1 Regression on 7/29/2026 2:44:38 PM +00:00
- Dominant language
- No language data
- Stars
- 10
- Forks
- 8
- PR merge metrics
- PR metrics pending
Description
### Run Information
Name | Value
-- | --
Architecture | x86
OS | Windows 10.0.22631
Queue | ViperWindows
Baseline | [00fc09ea5b2e39c46d56fda130b6693e07d449d8](https://github.com/dotnet/runtime/commit/00fc09ea5b2e39c46d56fda130b6693e07d449d8)
Compare | [0a25043f48f83ecfa896966929f25f792463344b](https://github.com/dotnet/runtime/commit/0a25043f48f83ecfa896966929f25f792463344b)
Diff | [Diff](https://github.com/dotnet/runtime/compare/00fc09ea5b2e39c46d56fda130b6693e07d449d8...0a25043f48f83ecfa896966929f25f792463344b)
Configs | CompilationMode:tiered, RunKind:micro
### Regressions in System.Threading.Tasks.Tests.Perf_AsyncMethods
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [Yield - 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 'System.Threading.Tasks.Tests.Perf_AsyncMethods*'
```
### System.Threading.Tasks.Tests.Perf_AsyncMethods.Yield
#### 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 System.Threading.Tasks.Tests.Perf_AsyncMethods.Yield benchmark source at src/benchmarks/micro/libraries/System.Threading.Tasks/Perf.AsyncMethods.cs and run the provided benchmarks_ci.py command. Compare the listed baseline and test commits, then use the profiling workflow to investigate the regression. Done means identifying the cause and validating the result against the reported performance difference.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, performance, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100