Reduce memory usage for EstablishDisaggRequest
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
EstablishDisaggRequest serializes ColumnFileInMemory into the gRPC request, so that it can use memory very quickly. In the example above, each Establish request eats ~70MB.
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 tracing EstablishDisaggRequest and how it serializes ColumnFileInMemory into the gRPC request. Measure the memory used by an Establish request against the reported roughly 70 MB example. Done means the request no longer causes that excessive memory growth while preserving the required serialization behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, grpc
- Domain
- distributed-systems, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100