[Performance] Investigate requirement of One Shard One Thread Model
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11
- Forks
- 17
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 5
Description
Goal:
To investigate and decide should we have one shard one thread model in I/O path.
Pros:
- Sequentialize I/O on HDD drives which can boost performance.
Cons
- any additional work in iomgr ??
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
The issue does not name any files, tests, or entry points. Begin by locating the I/O path and shard scheduling code, then assess whether a one-shard-one-thread model improves HDD sequential I/O without adding unacceptable I/O-manager work. Done means documenting a clear decision and its performance and implementation implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100