dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 1 Improvement on 7/10/2026 10:12:10 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 | [99eb16b5420fe88e333e2d95600b8617a86d54ff](https://github.com/dotnet/runtime/commit/99eb16b5420fe88e333e2d95600b8617a86d54ff)
Compare | [26b900856a2f12c4c7126827cb3019accba8f17c](https://github.com/dotnet/runtime/commit/26b900856a2f12c4c7126827cb3019accba8f17c)
Diff | [Diff](https://github.com/dotnet/runtime/compare/99eb16b5420fe88e333e2d95600b8617a86d54ff...26b900856a2f12c4c7126827cb3019accba8f17c)
Configs | AOT:true, CompilationMode:wasm, RunKind:micro
### Improvements in System.Threading.Channels.Tests.SpscUnboundedChannelPerfTests
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [TryWriteThenTryRead - 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
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.Threading.Channels.Tests.SpscUnboundedChannelPerfTests*'
```
### System.Threading.Channels.Tests.SpscUnboundedChannelPerfTests.TryWriteThenTryRead
#### 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.Channels.Tests.SpscUnboundedChannelPerfTests.TryWriteThenTryRead benchmark and reproduce it with the provided benchmarks_ci.py command. Compare the reported baseline and test results using the linked report and commits. The issue does not define a code change or acceptance condition, so the expected outcome needs triage before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, wasm
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100