`splinter_test --seq-perf` key generation is not coherent between insertion and lookup phases
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 732
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
It uses key generation that is based on thread_number and insert_number, but then it uses a global counter with batching to determine the insert_number, so that which thread_number, insert_number pairs are inserted is non-deterministic. As a result, the lookup phase always fails unless a single thread is used for both insertion and lookups.
Contributor guide
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 at the splinter_test --seq-perf entry point and trace key generation in both the insertion and lookup phases. Compare how thread_number and insert_number are assigned, then verify with a multi-threaded --seq-perf run that inserted keys are found during lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100