[MPP worker] optimize exchange operator to fully use network throughput
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Why
The network utilization decides the performance of MPP, we should carefully design and implement the exchange operator.
What
Optimize the exchange operator to fully use the network throughtput. Like KRPC 实现 Impala 的飞跃, we should let the RPC framework can scale out to many nodes.
How
efficiently multiplex resources: build almost one TCP connection among any two nodes using one thread;
support high concurrency when the computation part reads/writes from/into the data buffer in the exchange operator;
support data compression.
Check
building a test to collect the cost time of shuffle, as well as recoding the network
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 MPP worker exchange operator and the shuffle path described in the issue. Define and run a benchmark that measures shuffle time and records network utilization; completion requires evaluating multiplexed node connections, concurrent buffer reads and writes, and data compression against network throughput.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, networking, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100