Towards Benchmarking IaaS and PaaS Clouds for Graph Analytics

Conference paper (2014)

Authors

A. Iosup Data-Intensive Systems - EEMCS
M. Capota Data-Intensive Systems - EEMCS
T.M. Hegeman Data-Intensive Systems - EEMCS
Y. Guo Data-Intensive Systems - EEMCS
W.L. Ngai Data-Intensive Systems - EEMCS
A.L. Varbanescu Universiteit van Amsterdam
Merijn Verstraaten Universiteit van Amsterdam
Research Group
Data-Intensive Systems (EEMCS) (TU Delft)
More Info
expand_more

Published Date

2014

Language

English

Reuse Rights

Other than for strictly personal use, it is not permitted to download, forward or distribute the text or part of it, without the consent of the author(s) and/or copyright holder(s), unless the work is under an open content license such as Creative Commons.

Faculty

Electrical Engineering, Mathematics and Computer Science

Department

Software Technology

Research Group

Data-Intensive Systems

Abstract

Cloud computing is a new paradigm for using ICT services—only when needed and for as long as needed, and paying only for service actually consumed. Benchmarking the increasingly many cloud services is crucial for market growth and perceived fairness, and for service design and tuning. In this work, we propose a generic architecture for benchmarking cloud services. Motivated by recent demand for data-intensive ICT services, and in particular by processing of large graphs, we adapt the generic architecture to Graphalytics, a benchmark for distributed and GPU-based graph analytics platforms. Graphalytics focuses on the
dependence of performance on the input dataset, on the analytics algorithm,
and on the provisioned infrastructure. The benchmark provides components for platform configuration, deployment, and monitoring, and has been tested for a variety of platforms. We also propose a new challenge for the process of benchmarking data-intensive services, namely the inclusion of the data-processing algorithm in the system under test; this increases significantly the relevance of benchmarking results, albeit, at the cost of increased benchmarking duration.