This is not the latest version of this item. The latest version can be found here.
Amoeba: A shape changing storage system for big data
Name
3007263.3007311.pdf
Description
Published version
Size
363.12 KB
Format
Adobe PDF
Checksum (MD5)
ae475d22805458028644c55aa8d79456
Author(s)
Shanbhag, A
Jindal, A
Lu, Y
Madden, S
Date Issued
2016
Journal
Proceedings of the VLDB Endowment
Citation
Shanbhag, A, Jindal, A, Lu, Y and Madden, S. 2016. "Amoeba: A shape changing storage system for big data." Proceedings of the VLDB Endowment, 9 (13).
Version
Final published version
Abstract
© 2016 VLDB. Data partitioning significantly improves the query performance in distributed database systems. A large number of techniques have been proposed to efficiently partition a dataset for a given query workload. However, many modern analytic applications involve ad-hoc or exploratory analysis where users do not have a representative query workload upfront. Furthermore, workloads change over time as businesses evolve or as analysts gain better understanding of their data. Static workload-based data partitioning techniques are therefore not suitable for such settings. In this paper, we describe the demonstration of Amoeba, a distributed storage system which uses adaptive multi-attribute data partitioning to efficiently support ad-hoc as well as recurring queries. Amoeba applies a robust partitioning algorithm such that ad-hoc queries on all attributes have similar performance gains. Thereafter, Amoeba adaptively repartitions the data based on the observed query sequence, i.e., the system improves over time. All along Amoeba offers both adaptivity (i.e., adjustments according to workload changes) as well as robustness (i.e., avoiding performance spikes due to workload changes). We propose to demonstrate Amoeba on scenarios from an internet-of- things startup that tracks user driving patterns. We invite the audience to interactively fire fast ad-hoc queries, observe multi-dimensional adaptivity, and play with a robust/reactive knob in Amoeba. The web front end displays the layout changes, runtime costs, and compares it to Spark with both default and workload-aware partitioning.
Terms of Use
Creative Commons Attribution-NonCommercial-NoDerivs License
Persistent DSpace Link
DOI of Published Version
10.14778/3007263.3007311
