RAMCloud: Concept and Challenges John Ousterhout Stanford University.

Slides:



Advertisements
Similar presentations
Tivoli SANergy. SANs are Powerful, but... Most SANs today offer limited value One system, multiple storage devices Multiple systems, isolated zones of.
Advertisements

Fast Crash Recovery in RAMCloud
RAMCloud: Scalable High-Performance Storage Entirely in DRAM John Ousterhout Stanford University (with Nandu Jayakumar, Diego Ongaro, Mendel Rosenblum,
RAMCloud Scalable High-Performance Storage Entirely in DRAM John Ousterhout, Parag Agrawal, David Erickson, Christos Kozyrakis, Jacob Leverich, David Mazières,
RAMCloud 1.0 John Ousterhout Stanford University (with Arjun Gopalan, Ashish Gupta, Ankita Kejriwal, Collin Lee, Behnam Montazeri, Diego Ongaro, Seo Jin.
Log-Structured Memory for DRAM-Based Storage Stephen Rumble, Ankita Kejriwal, and John Ousterhout Stanford University.
Overview Of Microsoft New Technology ENTER. Processing....
SEDCL: Stanford Experimental Data Center Laboratory.
CS 140 Lecture Notes: Technology and Operating SystemsSlide 1 Technology Changes Mid-1980’s2009Change CPU speed15 MHz2 GHz133x Memory size8 MB4 GB500x.
Computer Science Storage Systems and Sensor Storage Research Overview.
Introducing the Platform Lab John Ousterhout Stanford University.
CS 142 Lecture Notes: Large-Scale Web ApplicationsSlide 1 RAMCloud Overview ● Storage for datacenters ● commodity servers ● GB DRAM/server.
Case Study - GFS.
1: IntroductionData Management & Engineering1 Course Overview: CS 395T Semantic Web, Ontologies and Cloud Databases Daniel P. Miranker Objectives: Get.
Metrics for RAMCloud Recovery John Ousterhout Stanford University.
Disaster Recovery as a Cloud Service Chao Liu SUNY Buffalo Computer Science.
RAMCloud Design Review Recovery Ryan Stutsman April 1,
A Compilation of RAMCloud Slides (through Oct. 2012) John Ousterhout Stanford University.
It’s Time for Low Latency Steve Rumble, Diego Ongaro, Ryan Stutsman, Mendel Rosenblum, John Ousterhout Stanford University 報告者 : 厲秉忠
Assumptions Hypothesis Hopes RAMCloud Mendel Rosenblum Stanford University.
What We Have Learned From RAMCloud John Ousterhout Stanford University (with Asaf Cidon, Ankita Kejriwal, Diego Ongaro, Mendel Rosenblum, Stephen Rumble,
1 The Google File System Reporter: You-Wei Zhang.
Chapter 10 : Designing a SQL Server 2005 Solution for High Availability MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design.
SEDCL/Platform Lab Retreat John Ousterhout Stanford University.
RAMCloud Overview John Ousterhout Stanford University.
RAMCloud: a Low-Latency Datacenter Storage System John Ousterhout Stanford University
Introduction and Overview Questions answered in this lecture: What is an operating system? How have operating systems evolved? Why study operating systems?
RAMCloud: A Low-Latency Datacenter Storage System Ankita Kejriwal Stanford University (Joint work with Diego Ongaro, Ryan Stutsman, Steve Rumble, Mendel.
Some key-value stores using log-structure Zhichao Liang LevelDB Riak.
Cool ideas from RAMCloud Diego Ongaro Stanford University Joint work with Asaf Cidon, Ankita Kejriwal, John Ousterhout, Mendel Rosenblum, Stephen Rumble,
John Ousterhout Stanford University RAMCloud Overview and Update SEDCL Forum January, 2015.
Improving Network I/O Virtualization for Cloud Computing.
Goodbye rows and tables, hello documents and collections.
Windows Azure Conference 2014 Deploy your Java workloads on Windows Azure.
1 Moshe Shadmon ScaleDB Scaling MySQL in the Cloud.
Low-Latency Datacenters John Ousterhout Platform Lab Retreat May 29, 2015.
Windows Azure Conference 2014 Designing Applications for Scalability.
Durability and Crash Recovery for Distributed In-Memory Storage Ryan Stutsman, Asaf Cidon, Ankita Kejriwal, Ali Mashtizadeh, Aravind Narayanan, Diego Ongaro,
DBI313. MetricOLTPDWLog Read/Write mixMostly reads, smaller # of rows at a time Scan intensive, large portions of data at a time, bulk loading Mostly.
RAMCloud: Low-latency DRAM-based storage Jonathan Ellithorpe, Arjun Gopalan, Ashish Gupta, Ankita Kejriwal, Collin Lee, Behnam Montazeri, Diego Ongaro,
RAMCloud: Scalable High-Performance Storage Entirely in DRAM John Ousterhout Stanford University (with Christos Kozyrakis, David Mazières, Aravind Narayanan,
File Processing : Storage Media 2015, Spring Pusan National University Ki-Joune Li.
Log-structured Memory for DRAM-based Storage Stephen Rumble, John Ousterhout Center for Future Architectures Research Storage3.2: Architectures.
Presenters: Rezan Amiri Sahar Delroshan
CS 140 Lecture Notes: Technology and Operating Systems Slide 1 Technology Changes Mid-1980’s2012Change CPU speed15 MHz2.5 GHz167x Memory size8 MB4 GB500x.
Fast Crash Recovery in RAMCloud. Motivation The role of DRAM has been increasing – Facebook used 150TB of DRAM For 200TB of disk storage However, there.
Experiences With RAMCloud Applications John Ousterhout, Jonathan Ellithorpe, Bob Brown.
RAMCloud Overview and Status John Ousterhout Stanford University.
VMware vSphere Configuration and Management v6
Implementing Linearizability at Large Scale and Low Latency Collin Lee, Seo Jin Park, Ankita Kejriwal, † Satoshi Matsushita, John Ousterhout Platform Lab.
Introduction.  Administration  Simple DBMS  CMPT 454 Topics John Edgar2.
 Introduction  Architecture NameNode, DataNodes, HDFS Client, CheckpointNode, BackupNode, Snapshots  File I/O Operations and Replica Management File.
CSci8211: Distributed Systems: RAMCloud 1 Distributed Shared Memory/Storage Case Study: RAMCloud Developed by Stanford Platform Lab  Key Idea: Scalable.
John Ousterhout Stanford University RAMCloud Overview and Update SEDCL Retreat June, 2013.
Presented by: Xianghan Pei
CS 140 Lecture Notes: Technology and Operating Systems Slide 1 Technology Changes Mid-1980’s2012Change CPU speed15 MHz2.5 GHz167x Memory size8 MB4 GB500x.
RAMCloud and the Low-Latency Datacenter John Ousterhout Stanford Platform Laboratory.
Amazon Web Services. Amazon Web Services (AWS) - robust, scalable and affordable infrastructure for cloud computing. This session is about:
St. Petersburg, 2016 Openstack Disk Storage vs Amazon Disk Storage Computing Clusters, Grids and Cloud Erasmus Mundus Master Program in PERCCOM Author:
Lecture 17 Raid. Device Protocol Variants Status checks: polling vs. interrupts Data: PIO vs. DMA Control: special instructions vs. memory-mapped I/O.
Log-Structured Memory for DRAM-Based Storage Stephen Rumble and John Ousterhout Stanford University.
Database Management Systems (CS 564)
CSE-291 Cloud Computing, Fall 2016 Kesden
CSE-291 (Cloud Computing) Fall 2016 Gregory Kesden
File Processing : Storage Media
CS 140 Lecture Notes: Technology and Operating Systems
File Processing : Storage Media
Outline Virtualization Cloud Computing Microsoft Azure Platform
CS 140 Lecture Notes: Technology and Operating Systems
Internet and Web Simple client-server model
Presentation transcript:

RAMCloud: Concept and Challenges John Ousterhout Stanford University

April 10, 2009RAMCloudSlide 2 Introduction ● RAMCloud: massive datacenter storage entirely in DRAM ● New research project:  Kozyrakis  Mazieres  McKeown  Mitra  Ousterhout  Parulkar  Prabhakar  Rosenblum ● Goal for today: feedback  What are we missing?  Related work  Pitfalls

April 10, 2009RAMCloudSlide 3 Outline ● Overview of RAMCloud ● Motivation ● Challenges in making RAMCloud a reality

April 10, 2009RAMCloudSlide 4 RAMCloud Overview ● Storage for datacenters ● commodity servers ● 64 GB DRAM/server ● All data always in RAM ● Low-latency access: 5-10µs RPC ● High throughput: 1,000,000 ops/sec/server ● High level of durability & availability Application Servers Storage Servers Datacenter

April 10, 2009RAMCloudSlide 5 Example Configurations Today5-10 years # servers1000 GB/server64GB1024GB Total capacity64TB1PB Total server cost$4M $/GB$60$4

April 10, 2009RAMCloudSlide 6 RAMDisk Motivation ● Relational databases don’t scale ● Every large-scale Web application has problems:  Facebook: 4000 MySQL instances memcached servers ● New forms of storage starting to appear:  Google BigTable ● Many apps don’t need all RDBMS features, can’t afford them

April 10, 2009RAMCloudSlide 7 RAMDisk Motivation, cont’d Disk access rate not keeping up with capacity: ● Disks must become more archival ● Can’t afford small random accesses ● RAM cost today = disk cost 10 years ago Mid-1980’sTodayChange Disk capacity30 MB200 GB6667x Max. transfer rate2 MB/s100 MB/s50x Latency (seek & rotate)20 ms10 ms2x Capacity/bandwidth (large blocks) 15 s2000 s133x Capacity/bandwidth (200B blocks) 3000 s115 days3333x

April 10, 2009RAMCloudSlide 8 Can We Make RAMCloud Work? ● Is capacity sufficient? ● Data durability/availability ● Low-latency RPCs ● Data model ● Concurrency model ● Data distribution, scaling ● Multi-tenancy ● Functional distribution ● Automated management

April 10, 2009RAMCloudSlide 9 Is RAMCloud Capacity Sufficient? ● Target applications: online data, not media ● Facebook: 200 TB of (non-image) data today ● Amazon: Revenues/year:$16B Orders/year:400M? ($40/order?) Bytes/order:10000? Order data/year4 TB? ● United Airlines: Total flights/day:4000? (30,000 for all airlines in U.S.) Passenger flights/year:200M? Data/passenger-flight:10000? Order data/year:2 TB?

April 10, 2009RAMCloudSlide 10 Data Durability/Availability ● Data must be durable when write RPC returns. ● Non-starters:  Synchronous disk write ( x too slow)  Replicate in other memories (too expensive) ● One possibility:  Log operations in RAM of other server(s)  Log to disk in batches  Occasional disk checkpoints to truncate logs ● Additional issues:  Fast recovery  Role of flash memory  Datacenter disaster recovery

April 10, 2009RAMCloudSlide 11 Low-Latency RPCs Achieving 5-10µs will impact every layer of the system: ● Network: cut-through routing, flow control ● OS:  Dedicated cores  No interrupts?  No virtual memory? ● Protocol stack  TCP too slow (especially with packet loss)  Must avoid copies ● Storage service Could we someday get to 1µs??

April 10, 2009RAMCloudSlide 12 Data Model ● Probably not relations:  Too rigid  Too much fragmentation  Better to collect larger objects? ● Unstructured blobs? ● Hierarchical hash tables (e.g. JSON)? ● What is the role of indexing?

April 10, 2009RAMCloudSlide 13 Concurrency Model ● Locking ● Transactions? ● What level of consistency for operations on distributed data?

April 10, 2009RAMCloudSlide 14 Distribution and Scaling ● How to distribute data among storage servers?  Concentrate to minimize RPCs, simplify consistency  Distribute to reduce hot spots ● How to achieve locality of access? (Is there any locality for Web apps?) ● Smooth scaling:  Automatic redistribution of data

April 10, 2009RAMCloudSlide 15 Multi-Tenancy ● Design for cloud computing environments:  Multiple users/applications sharing a RAMCloud ● Security/access control issues ● Scale down as well as up  Small apps should get RAMCloud benefits at proportional cost

April 10, 2009RAMCloudSlide 16 Functional Distribution ● RAMCloud will include software on both application servers and storage servers ● What is the right distribution? ● Application servers:  Offload storage system, increase scalability, flexibility  Example: aggregation operators ● Storage servers:  More trusted  May benefit from knowledge of internals Application Servers Storage Servers RAMCloud Software

April 10, 2009RAMCloudSlide 17 Automated Management ● Manual management a non-starter: system too complex ● Things that must be automatic:  Recovery from failures  Distribution of data among servers  Reorganization as system scales

April 10, 2009RAMCloudSlide 18 Discussion ● Why hasn’t this been done before? Or has it? ● If this is a good idea, what happened to main- memory databases? ● What are the biggest issues that might keep RAMCloud from working? ● What’s the most important database work we should be aware of? ● Would any of you like to participate in RAMCloud?