mlsanityData to 7 Oct 2026

Improving Spark Application Throughput Via Memory Aware Task Co-location: A Mixture of Experts Approach

arXiv 1710.00610 ↗First posted 2 Oct 2017cs.DCcited by 5

Not on the map. Why?

Abstract (arXiv)

Data analytic applications built upon big data processing frameworks such as Apache Spark are an important class of applications. Many of these applications are not latency-sensitive and thus can run as batch jobs in data centers. By running multiple applications on a computing host, task co-location can significantly improve the server utilization and system throughput. However, effective task co-location is a non-trivial task, as it requires an understanding of the computing resource requirement of the co-running applications, in order to determine what tasks, and how many of them, can be co-located. In this paper, we present a mixture-of-experts approach to model the memory behavior of Spark applications. We achieve this by learning, off-line, a range of specialized memory models on a range of typical applications; we then determine at runtime which of the memory models, or experts, best describes the memory behavior of the target application. We show that by accurately estimating the resource level that is needed, a co-location scheme can effectively determine how many applications can be co-located on the same host to improve the system throughput, by taking into consideration the memory and CPU requirements of co-running application tasks. Our technique is applied to a set of representative data analytic applications built upon the Apache Spark framework. We evaluated our approach for system throughput and average normalized turnaround time on a multi-core cluster. Our approach achieves over 83.9% of the performance delivered using an ideal memory predictor. We obtain, on average, 8.69x improvement on system throughput and a 49% reduction on turnaround time over executing application tasks in isolation, which translates to a 1.28x and 1.68x improvement over a state-of-the-art co-location scheme for system throughput and turnaround time respectively.

Key facts. Cited by 5 papers in the map (data through 7 Oct 2026). First posted on arXiv 2 Oct 2017.

Builds on

No reference list yet.

Built on by

Cited by year

Citing papers per year: 2021: 1; 2022: 1; 2023: 2; 2024: 1.

5 papers.

Similar, not cited

Close in wording, no citation either way

  1. 2025Zero-Execution Retrieval-Augmented Configuration Tuning of Spark Applications ↗
  2. 2026BatchBench: Toward a Workload-Aware Benchmark for Autoscaling Policies in Big Data Batch Processing -- A Proposed Framework ↗
  3. 2025The Streaming Batch Model for Efficient and Fault-Tolerant Heterogeneous Execution
  4. 2026MAPS: Memory-Aware Predictive Scheduling Framework for Large Language Model Serving
  5. 2026SparKV: Overhead-Aware KV Cache Loading for Efficient On-Device LLM Inference
  6. 2026SeqMoE: Toward Full-Load Performance via Predictive and Graph-Compatible MoE Offloading
  7. 2025SageServe: Optimizing LLM Serving on Cloud Data Centers with Forecast Aware Auto-Scaling
  8. 2025Echo: Efficient Co-Scheduling of Hybrid Online-Offline Tasks for Large Language Model Serving