cameron314 / cameron314/concurrentqueue
Prepare enqueue API
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.5k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
As for today we have bulk operations which reduce synchronization costs in average but it has high latency as we should move many elements at once. And I think API like queue.prepare_enqueue(max_count) -> output_iterator, "write to output iterator many times without sync", std::move(output_iterator).commit() would distribute moving values into many write calls.
The issue describes only enqueue, because underlying queues are single-producer ones, so it should be much easier than multiple-consumer synchronization
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing bulk operations and single-producer enqueue implementation, then compare their synchronization and latency behavior. Define the prepare_enqueue, output_iterator, and commit behavior described in the issue, and validate enqueue correctness and reduced synchronization; no file or test path is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100