performance: possible degradation after a lot of releases
Open
Nobody has claimed this yet.
performance
- Dominant language
- Lua
- Stars
- 244
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
@andrew-statsenko proposed to verify the following case against possible performance degradation.
- 1000 puts;
- 100 take+ack;
- 900 take+release;
- Repeat from 1.
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
Reproduce the listed workload using the queue's put, take+ack, and take+release operations, repeating the sequence as described. Measure performance across repetitions and document whether degradation occurs, including the conditions and evidence needed to consider the issue resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100