|国家预印本平台
首页|To Ship or Not to (Function) Ship (Extended version)

To Ship or Not to (Function) Ship (Extended version)

To Ship or Not to (Function) Ship (Extended version)

来源:Arxiv_logoArxiv
英文摘要

Sampling is often used to reduce query latency for interactive big data analytics. The established parallel data processing paradigm relies on function shipping, where a coordinator dispatches queries to worker nodes and then collects the results. The commoditization of high-performance networking makes data shipping possible, where the coordinator directly reads data in the workers' memory using RDMA while workers process other queries. In this work, we explore when to use function shipping or data shipping for interactive query processing with sampling. Whether function shipping or data shipping should be preferred depends on the amount of data transferred, the current CPU utilization, the sampling method and the number of queries executed over the data set. The results show that data shipping is up to 6.5x faster when performing clustered sampling with heavily-utilized workers.

Feilong Liu、Niranjan Kamat、Spyros Blanas、Arnab Nandi

计算技术、计算机技术通信电子技术应用

Feilong Liu,Niranjan Kamat,Spyros Blanas,Arnab Nandi.To Ship or Not to (Function) Ship (Extended version)[EB/OL].(2018-07-29)[2025-08-10].https://arxiv.org/abs/1807.11149.点此复制

评论