does it make sense to add concurrent benches?
Open
question
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 1.3k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 169
Description
**Which part is this question about**
arrow-rs or parquet
**Describe your question**
Right now the parquet/arrow benches are mostly single-reader / single-query shape. Wondering if it make sense to add concurrent read benches to answer questions like how multiple readers interact on the same file.
Contributor guide
Research direction
Start by reviewing the existing parquet/arrow benchmarks and how they model single-reader and single-query workloads. Determine what concurrent readers sharing one file should measure and how completion would demonstrate useful interaction data without changing the benchmark scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100