Need more tonic::Channel to each tikv-server
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 425
- Forks
- 163
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 3
Description
In the current implementation, the Client has only one TiKVConnect for each TiKV, which is essentially a single tonic::Channel underneath, meaning there's only one TCP connection. I made a simple modification to it, changing it to 16 channels per TiKV, and the OPS directly increased by 10 times. Perhaps we really need a connection pool.
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 reading the current Client and TiKVConnect implementation to locate how tonic::Channel connections are created and owned. Compare the single-channel behavior with the reported 16-channel modification, then define and validate a connection-pooling approach using the OPS improvement as the success measure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100