The Case for Workflow-Aware Storage:An Opportunity Study

• Published in: Journal of grid computing Vol. 13; no. 1; pp. 95 - 113
• Main Authors: Costa, L. B., Yang, H., Vairavanathan, E., Barros, A., Maheshwari, K., Fedak, G., Katz, D., Wilde, M., Ripeanu, M., Al-Kiswany, S.
• Format: Journal Article
• Language: English
• Published: Dordrecht Springer Netherlands 01.03.2015; Springer Nature B.V; Springer Verlag
• Subjects: Computational grids; Computer Science; Construction; Decisions; Design optimization; Distributed, Parallel, and Cluster Computing; Gain; Management of Computing and Information Systems; Optimization; Processor Architectures; Storage systems; User Interfaces and Human Computer Interaction; Vanilla; Workflow; storage system; Large-scale storage system; Workflow-aware; Workflow runtime engine; Large-scale storage system· Workflow-aware· Storage system· Workflow runtime engine
• ISSN: 1570-7873; 1572-9184
• DOI: 10.1007/s10723-014-9307-6

This article evaluates the potential gains a workflow-aware storage system can bring. Two observations make us believe such storage system is crucial to efficiently support workflow-based applications: First, workflows generate irregular and application-dependent data access patterns. These patterns render existing generic storage systems unable to harness all optimization opportunities as this often requires enabling conflicting optimizations or even conflicting design decisions at the storage system level. Second, most workflow runtime engines make suboptimal scheduling decisions as they lack the detailed data location information that is generally hidden by the storage system. This paper presents a limit study that evaluates the potential gains from building a workflow-aware storage system that supports per-file access optimizations and exposes data location. Our evaluation using synthetic benchmarks and real applications shows that a workflow-aware storage system can bring significant performance gains: up to 3x performance gains compared to a vanilla distributed storage system deployed on the same resources yet unaware of the possible file-level optimizations.