infiniflow / infiniflow/infinity
[Refactor]: No lock access block version
Open
Nobody has claimed this yet.
feature request
refactor
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 445
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 7
Description
Describe the improvement you'd like
A lock is used when infinity access block version. This issue proposes to use atomic variable to control the block version access to improve the performance.
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
The issue does not name files, tests, or an entry point. Start by locating the implementation of the infinity access block version and examine how its lock controls access; then identify relevant concurrency or performance tests. Done means the access control uses an atomic variable instead of the lock without changing behavior or regressing those tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100