Use async grpc server for cop and batch request to reduce thread creating and releasing.
Open
Nobody has claimed this yet.
type/enhancement
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Enhancement
we should use async grpc server for cop and batch request to reduce thread creating and releasing.
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 locating the gRPC server paths handling cop and batch requests in the TiFlash repository, then compare their current thread and server behavior with the available async gRPC approach. Confirm how request handling and shutdown are coordinated before defining the change. Done means both request types use the async server model and thread creation and release are reduced without changing request behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, grpc
- Domain
- api, backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100