Download presentation
Presentation is loading. Please wait.
Published byChristian Jenkins Modified over 9 years ago
1
@andy_pavl o OLTP on the NVM SDV: YMMV
2
2013 January Retreat Thesis Defense December Retreat Job Interviews Moved to CMU
3
2013 January Retreat Thesis Defense December Retreat Job Interviews Moved to CMU ?
8
8 Prison Life Washing Dishes Not Fighting Repentant Cafeteria Thievery Shankings Making Pruno G O OD EV IL
9
9 NVM OLTP Lightweight CC Logical Logging Snapshots Heavyweight CC ARIES Logging Making Pruno DR AM SSD/ HDD
10
Project Overview 10 Understand the performance characteristics of NVM to develop an optimal DBMS architecture for it.
11
Current Research Status 11 Compare DBMS architectures: –H-Store with Logging → NVM –Anti-Caching → NVM (block) –Anti-Caching → NVM (tuple) –H-Store with MMAP → NVM
12
H-Store – NVM Edition 12 Converted storage manager to use NVM through MMAP: –Table tuple storage. –VARCHAR/BLOB data pool. –Table indexes.
13
H-Store – NVM Edition 13 Minor changes to exec engine: –Group commit (msync) Current implementation is not transactional fail- safe.
14
Experimental Evaluation 14 Compare two architectures: –H-Store with MMAP → NVM –MySQL → NVM Yahoo! Cloud Serving Benchmark: –10 million records (~10GB) –8x database / memory MySQL
15
15 YCSB // TXN/SEC MySQL→NVM H-Store→NVM Read-Only Workload 2x Latency Relative to DRAM
16
16 YCSB // TXN/SEC Read-Only Workload 16x Latency Relative to DRAM ↓ 11% ↓ 29% MySQL→NVM H-Store→NVM
17
17 YCSB // TXN/SEC 50% Reads / 50% Writes Workload 2x Latency Relative to DRAM MySQL→NVM H-Store→NVM
18
18 YCSB // TXN/SEC 50% Reads / 50% Writes Workload 16x Latency Relative to DRAM ↓ 13% ↓ 8% MySQL→NVM H-Store→NVM
19
Discussion 19 Overhead is only from reads and msync syscalls. We’re not doing anything special with the NVM. –Contents of NVM are ignored for crash recovery.
20
What’s Next? 20 Port snapshot code to use NVM. Improve MMAP storage manager. Full comparison + experiments. Start building the next system…
21
N-STORE
22
N-Store – Possibility #1 22 Keep DRAM. Hybrid OLTP/OLAP architecture: –Row Store → DRAM –Column Store → NVM Multi-faceted indexes.
23
N-Store – Possibility #2 23 Ditch DRAM. Instant recovery: –No snapshots. –No logging. NVM-friendly concurrency control scheme.
24
What do we need? 24 Be able to tune the msync latency of the NVM SDV. Custom malloc implementation that runs entirely of PMFS.
25
Andy Pavlo Col. Stan Zdonik Mike Stonebraker Justin DeBrabant Joy Arulraj Subramanya Dulloor Rajesh Sankaran Jeff Parkhurst
26
@ANDY _ PAVLO END
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.