cameron314 / cameron314/concurrentqueue
One thread, two consumer / producer tokens
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.5k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
For architecture reasons I'm creating a consumer and producer token each in two separate classes running on the same thread. So there are effectively two consumer tokens and two producer tokens used within the same thread. Theoretically I could
Is there a performance penalty to be expected when multiple tokens are used with the same thread? Or any other side effect?
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
The issue names separate consumer-token and producer-token classes used on one thread, but no files or tests. Start by locating those token APIs and their same-thread usage rules; done would be a documented, maintainer-confirmed explanation of performance penalties or other side effects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100