dotnet / dotnet/perf-autofiling-issues
[Perf] Linux/x64: 6 Improvements on 7/31/2026 4:48:31 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 | [ba8afceee83540ed1d867987483f74d4ad2cfae9](https://github.com/dotnet/runtime/commit/ba8afceee83540ed1d867987483f74d4ad2cfae9)
Compare | [d5c739f99fa75a37ea863b06dd8d31a51965c8be](https://github.com/dotnet/runtime/commit/d5c739f99fa75a37ea863b06dd8d31a51965c8be)
Diff | [Diff](https://github.com/dotnet/runtime/compare/ba8afceee83540ed1d867987483f74d4ad2cfae9...d5c739f99fa75a37ea863b06dd8d31a51965c8be)
Configs | CompilationMode:wasm, RunKind:micro
### Improvements in System.Collections.Tests.Perf_BitArray
Benchmark | Baseline | Test | Test/Base | Test Quality | Edge Detector | Baseline IR | Compare IR | IR Ratio
-- | -- | -- | -- | -- | -- | -- | -- | --
|
- [BitArrayByteArrayCtor - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [BitArrayByteArrayCtor - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [BitArraySetLengthShrink - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [BitArraySetLengthShrink - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [BitArraySetLengthGrow - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
|
- [BitArraySetLengthGrow - Duration of single invocation]()
- 📝 - [Benchmark Source]()
- [ADX - Test Multi Config Graph]()
![graph]()
![graph]()
![graph]()
![graph]()
![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.Collections.Tests.Perf_BitArray*'
```
### System.Collections.Tests.Perf_BitArray.BitArrayByteArrayCtor(Size: 4)
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Collections.Tests.Perf_BitArray.BitArrayByteArrayCtor(Size: 512)
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Collections.Tests.Perf_BitArray.BitArraySetLengthShrink(Size: 512)
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Collections.Tests.Perf_BitArray.BitArraySetLengthShrink(Size: 4)
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Collections.Tests.Perf_BitArray.BitArraySetLengthGrow(Size: 4)
#### ETL Files
#### Histogram
#### JIT Disasms
### System.Collections.Tests.Perf_BitArray.BitArraySetLengthGrow(Size: 512)
#### 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 benchmark source at performance/src/benchmarks/micro/libraries/System.Collections/Perf.BitArray.cs#L49-L50 and #L120-L135, then run the provided benchmarks_ci.py command with the Perf_BitArray filter. Compare the six reported results under the Linux/x64 WASM configuration and determine whether they need follow-up.
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