DOCSLIB.ORG

Pocket: Elastic Ephemeral Storage for Serverless Analytics

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pocket: Elastic Ephemeral Storage for Serverless Analytics Pocket: Elastic Ephemeral Storage for Serverless Analytics Ana Klimovic1 Yawen Wang1 Patrick Stuedi 2 Animesh Trivedi2 Jonas Pfefferle2 Christos Kozyrakis1 1 Stanford University 2 IBM Research Abstract Pareto frontier Serverless computing is becoming increasingly popu- lar, enabling users to quickly launch thousands of short- lived tasks in the cloud with high elasticity and fine- grain billing. These properties make serverless comput- ing appealing for interactive data analytics. However exchanging intermediate data between execution stages in an analytics job is a key challenge as direct commu- nication between serverless tasks is difficult. The nat- ural approach is to store such ephemeral data in a re- mote data store. However, existing storage systems are not designed to meet the demands of serverless applica- tions in terms of elasticity, performance, and cost. We present Pocket, an elastic, distributed data store that au- Figure 1: Example of performance-cost trade-off for tomatically scales to provide applications with desired a serverless video analytics job using different storage performance at low cost. Pocket dynamically rightsizes technologies and VM types in Amazon EC2 resources across multiple dimensions (CPU cores, net- work bandwidth, storage capacity) and leverages multi- able parallelism in an analytics job and achieve near real- ple storage technologies to minimize cost while ensuring time performance [32, 45, 27]. In contrast to traditional applications are not bottlenecked on I/O. We show that serverless applications that consist of a single function Pocket achieves similar performance to ElastiCache Re- executed when a new request arrives, analytics jobs typ- dis for serverless analytics applications while reducing ically consist of multiple stages and require sharing of cost by almost 60%. state and data across stages of tasks (e.g., data shuffling). Most analytics frameworks (e.g., Spark) implement 1 Introduction data sharing with a long-running framework agent on each node buffering intermediate data in local stor- Serverless computing is becoming an increasingly popu- age [78]. This enables tasks from different execution lar cloud service due to its high elasticity and fine-grain stages to directly exchange intermediate data over the billing. Serverless platforms like AWS Lambda, Google network. However, in serverless deployments, there is Cloud Functions, and Azure Functions enable users to no long-running application framework agent to manage quickly launch thousands of light-weight tasks, as op- local storage. Furthermore, serverless applications have posed to entire virtual machines. The number of server- no control over task scheduling or placement, making di- less tasks scales automatically based on application de- rect communication among tasks difficult. As a result of mands and users are charged only for the resources their these limitations, the natural approach for data sharing in tasks consume, at millisecond granularity [17, 36, 56]. serverless applications is to use a remote storage service. While serverless platforms were originally developed For instance, early frameworks for serverless analytics for web microservices and IoT applications, their elas- either use object stores (e.g., S3 [16]), databases (e.g., ticity and billing advantages make them appealing for CouchDB [1]) or distributed caches (e.g., Redis [51]). data intensive applications such as interactive analytics. Unfortunately, existing storage services are not a good Several recent frameworks launch large numbers of fine- fit for sharing short-lived intermediate data in server- grain tasks on serverless platforms to exploit all avail- less applications. We refer to the intermediate data as ephemeral data to distinguish it from input and out- In summary, our contributions are as follows: put data which requires long-term storage. File sys- tems, object stores and NoSQL databases prioritize pro- • We identify the key characteristics of ephemeral viding durable, long-term, and highly-available storage data in serverless analytics and synthesize require- rather than optimizing for performance and cost. Dis- ments for storage platforms used to share such data tributed key-value stores offer good performance, but among serverless tasks. burden users with managing the storage cluster scale and • We introduce Pocket, a distributed data store whose configuration, which includes selecting the appropriate control, metadata and data planes are designed compute, storage and network resources to provision. for sub-second response times, automatic resource The availability of different storage technologies (e.g., scaling and intelligent data placement across stor- DRAM, NVM, Flash, and HDD) increases the complex- age tiers. To our knowledge, Pocket is the first plat- ity of finding the best cluster configuration for perfor- form targeting data sharing in serverless analytics. mance and cost. However, the choice of storage tech- • We show that Pocket’s data plane delivers sub- nology is critical since jobs may exhibit different stor- millisecond latency and scalable bandwidth while age latency, bandwidth and capacity requirements while the control plane rightsizes resources based on the different storage technologies vary significantly in terms number of jobs and their attributes. For a video an- of their performance characteristics and cost [48]. As alytics job, Pocket reduces the average time server- an example, Figure1 plots the performance-cost trade- less tasks spend on ephemeral I/O by up to 4.1× off for a serverless video analytics application using a compared to S3 and achieves similar performance distributed ephemeral data store configured with differ- to ElastiCache Redis while saving 59% in cost. ent storage technologies, number of nodes, compute re- sources per node, and network bandwidth (see §6.1 for Pocket is open-source software. The code is available our AWS experiment setup). Each resource configura- at: https://github.com/stanford-mast/pocket. tion leads to different performance and cost. Finding Pareto efficient storage allocations for a job is non-trivial 2 Storage for Serverless Analytics and gets more complicated with multiple jobs. We present Pocket, a distributed data store designed Early work in serverless analytics has identified the chal- for efficient data sharing in serverless analytics. Pocket lenge of storing and exchanging data between hundreds offers high throughput and low latency for arbitrary size of fine-grain, short-lived tasks [45, 32]. We build on our data sets, automatic resource scaling, and intelligent data study of ephemeral storage requirements for serverless placement across multiple storage tiers such as DRAM, analytics applications [49] to synthesize essential prop- Flash, and disk. The unique properties of Pocket result erties for an ephemeral data storage solution. We also from a strict separation of responsibilities across three discuss why current systems are not able to meet the planes: a control plane which determines data placement ephemeral I/O demands of serverless analytics applica- policies for jobs, a metadata plane which manages dis- tions. Our focus is on ephemeral data as the original in- tributed data placement, and a ‘dumb’ (i.e., metadata- put and final output data of analytics jobs typically has oblivious) data plane responsible for storing data. Pocket long-term availability and durability requirements that scales all three planes independently at fine resource and are well served by the variety of file systems, object time granularity based on the current load. Pocket uses stores, and databases available in the cloud. heuristics, which take into account job characteristics, to allocate the right storage media, capacity, bandwidth and CPU resources for cost and performance efficiency. The 2.1 Ephemeral Storage Requirements storage API exposes deliberately simple I/O operations High performance for a wide range of object sizes: for sub-millisecond access latency. We intend for Pocket Serverless analytics applications vary considerably in the to be managed by cloud providers and offered to users way they store, distribute, and process data. This diver- with a pay-what-you-use cost model. sity is reflected in the granularity of ephemeral data that We deploy Pocket on Amazon EC2 and evaluate the is generated during a job. Figure2 shows the ephemeral system using using three serverless analytics workloads: object size distribution for a distributed lambda compi- video analytics, MapReduce sort, and distributed source lation of the cmake program, a serverless video analyt- code compilation. We show that Pocket is capable ics job using the Thousand Island (THIS) video scan- of rightsizing the type and number of resources such ner [63], and a 100 GB MapReduce sort job on lamb- that jobs achieve similar performance compared to us- das. The key observation is that ephemeral data ac- ing ElastiCache Redis, a DRAM-based key-value store, cess granularity varies greatly in size, ranging from hun- while saving almost 60% in cost. dreds of bytes to hundreds of megabytes. We observe a 1.0 1.0 λ-cc cmake 0.8 video analytics 0.8 sort100GB 0.6 0.6 CDF CDF 0.4 0.4 λ-cc cmake 0.2 0.2 video-analytics sort 100 GB 0.0 1 2 3 4 5 6 7 8 0.0 10 10 10 10 10 10 10 10 0 20 40 60 80 100 Ephemeral Object Size (bytes) Ephemeral Object Lifetime (seconds) Figure 2: Objects are 100s of bytes to 100s of MBs. Figure 3: Objects have short lifetime. straight line for sorting as its ephemeral data size is equal The variety of storage media available in the cloud al- to the partition size. However, with a different dataset low for different performance-cost trade-offs, as shown size and/or number of workers, the location of the line in Figure1. Each storage technology differs in terms of changes. Applications that read/write large objects de- I/O latency, throughput and IOPS per GB of capacity, mand high throughput (e.g., we find that sorting 100 GB and the cost per GB. The optimal choice of storage me- with 500 lambdas requires up to 7.5 GB/s of ephemeral dia for a job depends on its characteristics.
Load more

Recommended publications
  • Using Alluxio to Optimize and Improve Performance of Kubernetes-Based Deep Learning in the Cloud
    Using Alluxio to Optimize and Improve Performance of Kubernetes-Based Deep Learning in the Cloud Featuring Alibaba Cloud Container Service Team Case Study What’s Inside 1 / New Trends in AI: Kubernetes-based This article presents the collaborative work of Deep Learning in the Cloud Alibaba, Alluxio, and Nanjing University in tackling the problem of Artificial Intelligence and Deep Learning 2 / Container and Data Orchestration model training in the cloud. We adopted a hybrid Based Architecture solution with a data orches-tration layer that connects 3 / Training in the Cloud - The First Take at private data centers to cloud platforms in a Alluxio Distributed Cache containerized environment. Various perfor-mance bottlenecks are analyzed with detailed optimizations of 4 / Performance Optimization of Model each component in the architecture. Our goal was to Training on the Cloud reduce the cost and complexity of data access for Deep 5 / Summary and Future Work Learning training in a hybrid environment, which resulted in over 40% reduction in training time and cost. © Copyright Alluxio, Inc. All rights reserved. Alluxio is a trademark of Alluxio, Inc. WHITEPAPER 1 / New trends in AI: Kubernetes-Based Deep Learning in the Cloud Background The rising popularity of artificial intelligence (AI) and deep learning (DL), where artificial neural networks are trained with increasingly massive amounts of data, continues to drive innovative solutions to improve data processing. Distributed DL model training can take advantage of multiple technologies, such as: • Cloud computing for elastic and scalable infrastructure • Docker for isolation and agile iteration via containers and Kubernetes for orchestrating the deployment of containers • Accelerated computing hardware, such as GPUs The merger of these technologies as a combined solution is emerging as the industry trend for DL training.
    [Show full text]
  • Alluxio Overview
    Alluxio Overview What’s Inside 1 / Introduction 2 / Data Access Challenges 3 / Benefits of Alluxio 4 / How Alluxio Works 5 / Enabling Compute and Storage Separation 6 / Use Cases 7 / Deployment © Copyright Alluxio, Inc. All rights reserved. Alluxio is a trademark of Alluxio, Inc. WHITEPAPER 1 / Introduction Alluxio is an open source software that connects analytics applications to heterogeneous data sources through a distribut- ed caching layer that sits between compute and storage. It runs on commodity hardware, creating a shared data layer abstracting the files or objects in underlying persistent storage systems. Applications connect to Alluxio via a standard interface, accessing data from a single unified source. Application Interface: Alluxio API / Hadoop Compatible / S3 Compatible / REST / FUSE Storage Interface: Any Object / File Storage WHITEPAPER / 2 2 / Data Access Challenges Organizations face a range of challenges while striving to extract value from data. Alluxio provides innovation at the data layer to abstract complexity, unify data, and intelligently manage data. This approach enables a new way to interact with data and connect the applications and people doing the work to the data sources, regardless of format or location. Doing so provides a solution to a range of challenges, for example: · Lack of access to data stored in storage silos across different departments and locations, on-premise and in the cloud · Difficulty in sharing data with multiple applications · Each application and storage system has its own interface and data exists in a wide range of formats · Data is often stored in clouds or remote locations with network latency slowing performance and impacting the freshness of the data · Storage is often tightly coupled with compute making it difficult to scale and manage storage independently / 3 3 / Benefits of Alluxio Alluxio helps overcome the obstacles to extracting value from data by making it simple to give applications access to what- ever data is needed, regardless of format or location.
    [Show full text]
  • Accelerate Big Data Processing (Hadoop, Spark, Memcached, & Tensorflow) with HPC Technologies
    Accelerate Big Data Processing (Hadoop, Spark, Memcached, & TensorFlow) with HPC Technologies Talk at Intel® HPC Developer Conference 2017 (SC ‘17) by Dhabaleswar K. (DK) Panda Xiaoyi Lu The Ohio State University The Ohio State University E-mail: [email protected] E-mail: [email protected] http://www.cse.ohio-state.edu/~panda http://www.cse.ohio-state.edu/~luxi Big Data Processing and Deep Learning on Modern Clusters • Multiple tiers + Workflow – Front-end data accessing and serving (Online) • Memcached + DB (e.g. MySQL), HBase, etc. – Back-end data analytics and deep learning model training (Offline) • HDFS, MapReduce, Spark, TensorFlow, BigDL, Caffe, etc. Network Based Computing Laboratory Intel® HPC Developer Conference 2017 2 Drivers of Modern HPC Cluster Architectures High Performance Interconnects - Accelerators / Coprocessors InfiniBand high compute density, high Multi-core Processors <1usec latency, 100Gbps Bandwidth> performance/watt SSD, NVMe-SSD, NVRAM >1 TFlop DP on a chip • Multi-core/many-core technologies • Remote Direct Memory Access (RDMA)-enabled networking (InfiniBand and RoCE) • Solid State Drives (SSDs), Non-Volatile Random-Access Memory (NVRAM), NVMe-SSD • Accelerators (NVIDIA GPGPUs and Intel Xeon Phi) Tianhe – 2 Titan Stampede Tianhe – 1A Network Based Computing Laboratory Intel® HPC Developer Conference 2017 3 Interconnects and Protocols in OpenFabrics Stack for HPC (http://openfabrics.org) Application / Middleware Application / Middleware Interface Sockets Verbs Protocol Kernel Space TCP/IP TCP/IP
    [Show full text]
  • Alluxio: a Virtual Distributed File System by Haoyuan Li A
    Alluxio: A Virtual Distributed File System by Haoyuan Li A dissertation submitted in partial satisfaction of the requirements for the degree of Doctor of Philosophy in Computer Science in the Graduate Division of the University of California, Berkeley Committee in charge: Professor Ion Stoica, Co-chair Professor Scott Shenker, Co-chair Professor John Chuang Spring 2018 Alluxio: A Virtual Distributed File System Copyright 2018 by Haoyuan Li 1 Abstract Alluxio: A Virtual Distributed File System by Haoyuan Li Doctor of Philosophy in Computer Science University of California, Berkeley Professor Ion Stoica, Co-chair Professor Scott Shenker, Co-chair The world is entering the data revolution era. Along with the latest advancements of the Inter- net, Artificial Intelligence (AI), mobile devices, autonomous driving, and Internet of Things (IoT), the amount of data we are generating, collecting, storing, managing, and analyzing is growing ex- ponentially. To store and process these data has exposed tremendous challenges and opportunities. Over the past two decades, we have seen significant innovation in the data stack. For exam- ple, in the computation layer, the ecosystem started from the MapReduce framework, and grew to many different general and specialized systems such as Apache Spark for general data processing, Apache Storm, Apache Samza for stream processing, Apache Mahout for machine learning, Ten- sorflow, Caffe for deep learning, Presto, Apache Drill for SQL workloads. There are more than a hundred popular frameworks for various workloads and the number is growing. Similarly, the storage layer of the ecosystem grew from the Apache Hadoop Distributed File System (HDFS) to a variety of choices as well, such as file systems, object stores, blob stores, key-value systems, and NoSQL databases to realize different tradeoffs in cost, speed and semantics.
    [Show full text]
  • Intel Select Solutions for HPC & AI Converged Clusters
    Solution Brief Intel® Select Solutions High Performance Computing and AI March 2021 Intel Select Solutions for HPC & AI Converged Clusters Intel Select Solutions deliver the compute-intensive resources needed to run artificial-intelligence (AI) workloads on existing high-performance computing (HPC) clusters. Enterprises are looking to simulation and modeling, artificial intelligence (AI), and big data analytics to help them achieve breakthrough discoveries and innovation. They understand these workloads benefit from a high-performance computing (HPC) infrastructure, yet they might still believe that separate HPC, AI, and big data clusters are the best choice for running these workloads. Contributing to this belief are two challenges. The first challenge is a fundamental difference in how workloads request resources and how HPC systems allocate them. AI and analytics workloads request compute resources dynamically, an approach that isn’t compatible with batch scheduling software used to allocate system resources in HPC clusters. The second challenge is the pattern of using computing systems based on graphics processing units (GPUs) as dedicated solutions for AI workloads. Enterprises might not realize that adding these workloads to an existing HPC cluster is feasible without the use of GPUs. Enterprises can deliver the compute infrastructure needed by AI workloads, with high levels of performance and cost-effectiveness, without adding the complexity of managing separate, dedicated systems. What they need is the ability to run HPC, big data analytics, and AI workloads within the same HPC infrastructure. They also need optimized resource scheduling that helps save time and reduce computing costs. Creating a converged platform to run HPC, AI, and analytics workloads in a single cluster infrastructure supports breakthrough innovation.
    [Show full text]
  • Best Practices
    Cloud Container Engine Best Practices Issue 01 Date 2021-09-07 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Issue 01 (2021-09-07) Copyright © Huawei Technologies Co., Ltd. i Cloud Container Engine Best Practices Contents Contents 1 Checklist for Deploying Containerized Applications in the Cloud...............................1 2 Cluster.......................................................................................................................................
    [Show full text]
  • A Solution for Bigdata Integrate with Ceph Inwinstack / Chief Architect Thor Chin Agenda
    A solution for BigData integrate with Ceph inwinSTACK / Chief Architect Thor Chin Agenda Why we need Ceph? Why we need to integrate Ceph with Big Data? How to integrate Ceph with Big Data? What’s Alluxio? Alluxio User List Architecture for Ceph integrate with Big Data Example Why we need Ceph? Distributed storage system - Fault tolerant , no SPoF X86 Commodity hardware - Saving you costs, giving you flexibility Large scale – Incremental expansion - 10s to 1000s of nodes Unified storage platform - Scalable object , Block , File system. Open source – No vender lock-in Automatically balance the file system Data security - with 2 or more copies in different physical store media. Why we need to integrate Ceph with Big Data? Separate Application and Data Better Architecture to solve Hadoop Name Node HA Issue Scalable storage solution High Performance How to integrate Ceph with Big Data? Through an Interface Alluxio: A Virtual Distributed Storage System What’s Alluxio Unified Access Thriving Community High Performance Alluxio is the unified access point Start from UC Berkeley Open Alluxio's memory-centric for your data. Applications only Source Project – Tachyon since architecture enables data access need to connect with Alluxio to 2013 Apr. released 16 versions orders of magnitudes faster than access data in all your under and rename to Alluxio release 1.0 existing solutions. storage systems. version in 2016 Feb. Fastest growing open source project in big data history with more than 200 contributors from over 50 organizations.
    [Show full text]
  • High Performance File System and I/O Middleware Design for Big Data on HPC Clusters
    High Performance File System and I/O Middleware Design for Big Data on HPC Clusters Dissertation Presented in Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy in the Graduate School of The Ohio State University By Nusrat Sharmin Islam, M.Sc. Graduate Program in Computer Science and Engineering The Ohio State University 2016 Dissertation Committee: Dr. Dhabaleswar K. (DK) Panda, Advisor Dr. Ponnuswamy Sadayappan Dr. Radu Teodorescu Dr. Xiaoyi Lu c Copyright by Nusrat Sharmin Islam 2016 Abstract Hadoop MapReduce and Spark are the two most popular Big Data processing frame- works of the recent time and Hadoop Distributed File System (HDFS) is the underlying file system for MapReduce, Spark, Hadoop Database, HBase as well as SQL query en- gines like Hive and Spark SQL. HDFS along with these upper-level middleware is now extensively being used on High Performance Computing (HPC) systems. The large-scale HPC systems, by necessity, are equipped with high performance interconnects like Infini- Band, heterogeneous storage devices like RAM Disk, SSD, HDD, and parallel file systems like Lustre. Non-Volatile Memory (NVM) is emerging and making its way into the HPC systems. Hence, the performance of HDFS, and in turn, the upper-level middleware and applications, is heavily dependent upon how it has been designed and optimized to take the system resources and architecture into account. But HDFS was initially designed to run over low-speed interconnects and disks on commodity clusters. As a result, it cannot efficiently utilize the resources available in HPC systems. For example, HDFS uses Java Socket for communication that leads to the overhead of multiple data copies and offers little overlapping among different phases of operations.
    [Show full text]
  • Scalable Collaborative Caching and Storage Platform for Data Analytics
    Scalable Collaborative Caching and Storage Platform for Data Analytics by Timur Malgazhdarov A thesis submitted in conformity with the requirements for the degree of Master of Applied Science Edward S. Rogers Sr. Department of Electrical and Computer Engineering University of Toronto c Copyright 2018 by Timur Malgazhdarov Abstract Scalable Collaborative Caching and Storage Platform for Data Analytics Timur Malgazhdarov Master of Applied Science Edward S. Rogers Sr. Department of Electrical and Computer Engineering University of Toronto 2018 The emerging Big Data ecosystem has brought about dramatic proliferation of paradigms for analytics. In the race for the best performance, each new engine enforces tight cou- pling of analytics execution with caching and storage functionalities. This one-for-all ap- proach has led to either oversimplifications where traditional functionality was dropped or more configuration options that created more confusion about optimal settings. We avoid user confusion by following an integrated multi-service approach where we assign responsibilities to decoupled services. In our solution, called Gluon, we build a collab- orative cache tier that connects state-of-art analytics engines with a variety of storage systems. We use both open-source and proprietary technologies to implement our archi- tecture. We show that Gluon caching can achieve 2.5x-3x speedup when compared to uncustomized Spark caching while displaying higher resource utilization efficiency. Fi- nally, we show how Gluon can integrate traditional storage back-ends without significant performance loss when compared to vanilla analytics setups. ii Acknowledgements I would like to thank my supervisor, Professor Cristiana Amza, for her knowledge, guidance and support. It was my privilege and honor to work under Professor Amza's supervision.
    [Show full text]
  • Spark on Docker Solutions
    Weiting Chen [email protected] Zhen Fan [email protected] INTEL NOTICE & DISCLAIMER No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. This document contains information on products, services and/or processes in development. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest forecast, schedule, specifications and roadmaps. The products and services described may contain defects or errors known as errata which may cause deviations from published specifications. Current characterized errata are available on request. Copies of documents which have an order number and are referenced in this document may be obtained by calling 1- 800-548-4725 or by visiting www.intel.com/design/literature.htm. Intel, the Intel logo, Intel® are trademarks of Intel Corporation in the U.S. and/or other countries. *Other names and brands may be claimed as the property of others Copyright © 2016 Intel Corporation. System Technologies & Optimization (STO) 2 AGENDA BACKGROUND SPARK ON KUBERNETES - Why Spark-on-K8s - How it works - Current Issues JD.COM CASE STUDY - Architecture - Network Choice - Storage Choice SUMMARY System Technologies & Optimization (STO) 3 System Technologies & Optimization (STO) 4 about spark-on-kubernetes https://github.com/apache-spark-on-k8s/spark Spark* on Kubernetes*(K8s) is a new project proposed by the companies including Bloomberg, Google, Intel, Palantir, Pepperdata, and Red Hat.
    [Show full text]
  • Kyle Bader - Red Hat Yuan Zhou, Yong Fu, Jian Zhang - Intel May, 2018 Agenda
    Kyle Bader - Red Hat Yuan Zhou, Yong Fu, Jian Zhang - Intel May, 2018 Agenda ▪ Background and Motivations ▪ The Workloads, Reference Architecture Evolution and Performance Optimization ▪ Performance Comparison with Remote HDFS ▪ Summary & Next Step Optimization Notice Copyright © 2018, Intel Corporation. All rights reserved. *Other names and brands may be claimed as the property of others. Optimization Notice Copyright © 2018, Intel Corporation. All rights reserved. *Other names and brands may be claimed as the property of others. DISCONTINUITY IN BIG DATA INFRASTRUCTURE - WHY ? CONGESTION in busy analytic clusters causing missed SLAs. HADOOP MULTIPLE TEAMS COMPETING and sharing the same big data resources. SPARKSQL HIVE PRESTO KAFKA SPARK MAPREDUCE IMPALA NiFi Optimization Notice Copyright © 2018, Intel Corporation. All rights reserved. *Other names and brands may be claimed as the property of others. MODERN BIG DATA ANALYTICS PIPELINE KEY TERMINOLOGY TRANSFORM, STREAM MERGE, DATA PROCESSING JOIN ANALYTICS DATA INGEST DATA MACHINE GENERATION SCIENCE LEARNING Optimization Notice Copyright © 2018, Intel Corporation. All rights reserved. *Other names and brands may be claimed as the property of others. MODERN BIG DATA ANALYTICS PIPELINE KEY TERMINOLOGY TRANSFORM, STREAM MERGE, DATA PROCESSING JOIN ANALYTICS • Kafka • Hadoop • Spark • Spark • Hadoop DATA INGEST DATA MACHINE GENERATION SCIENCE LEARNING • Sensors • NiFi • Presto • TensorFlow • Click-stream • Kafka • Impala • Transactions • SparkSQL • Call-detail records Optimization Notice Copyright © 2018, Intel Corporation. All rights reserved. *Other names and brands may be claimed as the property of others. DISCONTINUITY IN BIG DATA INFRASTRUCTURE - WHY ? CONGESTION in busy analytic clusters causing missed SLAs. HADOOP MULTIPLE TEAMS COMPETING and sharing the same big data resources. SPARKSQL HIVE PRESTO KAFKA SPARK MAPREDUCE IMPALA NiFi Optimization Notice Copyright © 2018, Intel Corporation.
    [Show full text]
  • A Benchmark for Suitability of Alluxio Over Spark
    International Journal of Innovative Technology and Exploring Engineering (IJITEE) ISSN: 2278-3075, Volume-10 Issue-1, November 2020 A Benchmark for Suitability of Alluxio over Spark Kanchana Rajaram, Kavietha Haridass Abstract: Big data applications play an important role in real applications to access data regardless of their formats and time data processing. Apache Spark is a data processing locations. Alluxio is used as a data access layer for Spark framework with in-memory data engine that quickly processes applications. Alluxio framework over Spark decouples large data sets. It can also distribute data processing tasks across storage and computation [4]. When used with Spark, Alluxio multiple computers, either on its own or in tandem with other persists the data even when the Spark shell is closed. It speeds distributed computing tools. Spark’s in-memory processing up I/O performance especially when data is stored remotely cannot share data between the applications and hence, the RAM memory will be insufficient for storing petabytes of data. Alluxio from Spark. When the data is locally stored, Spark by itself is a virtual distributed storage system that leverages memory for shows a good performance. Though Spark framework is data storage and provides faster access to data in different storage efficient for big data processing, it is required to identify the systems. Alluxio helps to speed up data intensive Spark need for using Alluxio with Spark. It is important to know applications, with various storage systems. In this work, the whether Alluxio on Spark would always provide better performance of applications on Spark as well as Spark running performance.
    [Show full text]