cameron314 / cameron314/concurrentqueue
Introducing LIFO semaphore
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.5k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
Hi dear developer,
Have you ever considered replacing the LightweightSemaphore in BlockingConcurrentQueue with a LIFO one to reduce unnecessary thread wake-ups in usage scenarios similar to threadpool?
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 reading BlockingConcurrentQueue and its LightweightSemaphore implementation to understand how semaphore waits and wake-ups currently work. Investigate whether a LIFO semaphore fits the queue's threadpool-like usage scenarios and define the behavioral and performance requirements. Done would require an agreed design and validation of the proposed replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100