orxfun / orxfun/orx-concurrent-queue
Allow for concurrent shrinking when makes sense
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Consider for instance using a SplitVec as the backing pinned vector. Whenever all elements of the first fragment are dropped, it can be dropped while the queue is being in use, rather than waiting it to be dropped. This would help minimize the maximum memory usage at any point in time. SplitVec with Linear growth strategy would benefit the most from this feature.
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 tracing the queue's pinned-vector growth and shrinking behavior, focusing on the proposed SplitVec backing vector and its Linear growth strategy. Done means the first fragment can be safely reclaimed while the queue remains in use, with coverage for the relevant shrinking behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100