Beyond Block I/O: Rethinking

Transcription

1 Beyond Block I/O: Rethinking Traditional Storage Primitives Xiangyong Ouyang *, David Nellans, Robert Wipfel, David idflynn, D. K. Panda * * The Ohio State University Fusion io

2 Agenda Introduction and Motivation Solid State Storage (SSS) Characteristics Duplicated efforts at SSS and upper layers Atomic Write Primitive within FTL Leverage Atomic Write in DBMS Example with MySQL Experimental Results Conclusion and Future Work 2

3 Evolution of Storage Devices Interface to persistent storage remains unchanged for decades seek, read, write Fits well with mechanical hard disks Solid State Storage (SSS) Merits Fast random access, high throughput Low power consumption Shockresistance resistance, smallform factor Expose the same disk based block I/O interface Challenges 3

4 NAND flash Based Solid State Storage (SSS) Pitfalls Asymmetric read/write latency Cannot overwrite before erasure Erasure at large unit ( pages), very slow (+ ms) Flash Wear out: limited write durability SLC: 30K erase/program cycles, MLC: 3K erase/program cycles Flash Translation Layer (FTL) Input: Logical Block Address (LBA) Output: Physical Block Address (PBA) File System OS Applications i Flash Translation Layer Flash Media 4

5 Log Structured FTL Mapping LBA >PBA Log head Log tail PBA:

6 Log Structured FTL Write Request Mapping LBA >PBA Log head Log tail Log taillog tail PBA: Log FTL Advantages Avoid in place update (Block Remapping) Even wear leveling 6

7 Duplicated Efforts at Upper Layers and FTL Multi Version at Upper Layer DBMS ( Transactional Log ) File systems (Metadata journaling, Copy on Write) To achieve Write Atomicity ACID: Atomicity, Consistency,Isolation,durability Block Remapping at FTL Avoid idin place update dt in critical path Common Thread: Multi versions of same data Why duplicate this effort? Proposed approach: Offload Write Atomicity guarantee to FTL Provide Atomic Write Wit primitive iti to upper layers 7

8 Agenda Introduction and Motivation Atomic Write Primitive at FTL Leverage Atomic Write in DBMS Experimental Results Conclusion and Future Work 8

9 Atomic Write: a New Block I/O Primitive Offloadthe Write Atomicity guaranteeinto FTL Combines multi block writes into a logical lgroup (contiguous, non contiguous) Commit the group as an atomic unit, if the compound operation succeeds Rollback the whole group is any individual fails 9

10 Atomic Write (): Flag Bit in Block Header One FlagBit per block header Identify blocks belonging to the same atomic group Non AW: flag == Atomic Write Flags== 0 0 Log tail Flag Bit LBA PBA Don t allow Non AW to interleave with Atomic Write 0

11 Atomic Write (2): Deferred Mapping Table Update Defer mapping table update Not expose partial state to readers Mapping LBA >PBA Incoming Atomic Write Group Log tail Log tail Log tail PBA:

12 Atomic Write (3): Failure Recovery Atomic Write Group Write LBA 4, 6, 8 Update Mapping (3) Failure when updating FTL Incomplete Atomic Write group () Failure during writing: Scan backwards, discard blocks with 0 flag bits Rollback the partial blocks to previous version complete Atomic Write group (2) Failure after writing Scan the log from beginning, g, rebuild the FTL mapping Log g tail contains flag bit Same as (2) 2

13 Agenda Introduction and Motivation Atomic Write Primitive at FTL Leverage Atomic Write in DBMS Example with MySQL Experimental Results Conclusion and Future Work 3

14 Proposed Storage Stack DBMS Applications File System Write Atomicity Generalized Solid State Storage Layer Wear Leveling More Solid State Storage Example: Leverage Atomic Write in DBMS ( MySQL ) 4

15 DoubleWrite with MySQL InnoDB Storage Engine DoubleWrite Buffer Flush dirty buffer pages to TableFile memory pressure commit() Timeout Buffer Pool Phase I Phase II Memory Stable Storage Table File: DoubleWrite Area TableSpace Area Every data page is written twice! Impact the performance Double amount of writes to Flash media halve device s lifespan 5

16 MySQL InnoDB: Atomic Write Buffer Pool int atomic_write (int fd, void* buf[], long *length[], long * offsets[], int num); Memory Stable Storage Table File: Reduce the data written by half Double the effective wear out life Simplify the upper layer design Better performance Guarantee the same level of data integrity as DoubleWrite 6

17 Agenda Introduction and Motivation Atomic Write Primitive at FTL Leverage Atomic Write in DBMS Experimental Results Conclusion and Future Work 7

18 Experiment Setup Fusion io 320GB MLC NAND flash based device Atomic Write implemented in a research branch of v2. Fusion io driver MySQL InnoDB (extendedwithatomic Write) 2 machines connected with GigE Both Trans. log and table file stored on solid state Processor Xeon 2.3GHz DRAM 8GB DDR2 667MHz, 4X2GB Boot Device 250GB SATA II 3.0Gb/s DB Storage Device Fusion io iodrive 320GB PCIe 04x.0 Lanes OS Ubuntu 9.0, Linux Kernel

19 Micro Benchmark Different Write Mechanisms: Synchronous: write() + fsync() Asynchronous: libaio Atomic Write Wit Different write patterns: Sequential Strided Random Buffer strategies Buffered_IO: OS page cache Direct_IO: bypasses OS page cache 9

20 I/O Microbenchmark: Latency Write Latency (Lower is Better) ( 64blocks blocks, 52Beach) Latency (us) Write Buffering Write Strategy Pattern Sync Async A Write Random Buffered NA DirectIO Strided Buffered NA DirectIO Sequential Buffered NA DirectIO Atomic Write : all blocks in onecompoundwrite Synchronous Write: write ( ) + fsync( ) Asynchronous Write: Linux libaio 20

21 I/O Microbenchmark: Bandwidth Write Bandwidth (Higher is Better) ( 64blocks blocks, 6KBeach) Bandwidth (MB/s) Write Buffering Write Strategies Pattern Sync Async A Write Random Buffered NA DirectIO Strided Buffered NA DirectIO Sequential Buffered NA DirectIO Atomic Write : all blocks in onecompoundwrite Synchronous Write: write ( ) + fsync( ) Asynchronous Write: Linux libaio 2

22 8% improvement (not ACID compliant).4 Transaction Throughput 23% improvement (ACID compliant) MySQL DoubleWrite Disabled Atomic Write hroughpu ut Tran nsaction T TPC C TPC H SysBench Buffer Pool : Database = : 0 DB workload: TPC C (DBT2), TPC H (DBT3), SysBench 22

23 Data Written to SSS.2 MySQL DoubleWrite Disabled Atomic Write Data a Written % reduction TPC C TPC H sysbench (not ACID compliant) 43% reduction (ACID compliant) (High throughput generate more trans. log) Buffer Pool : Database = : 0 DB workload: TPC C (DBT2), TPC H (DBT3), SysBench 23

24 .2 Transaction Latency MySQL DoubleWrite Disabled Atomic Write ion Laten ncy Transact TPC C TPC H sysbench 9% improvement 20% improvement (not ACID compliant) (ACID compliant) Buffer Pool : Database = : 0 DB workload: TPC C (DBT2), TPC H (DBT3), SysBench 24

25 DB buffer pool size : DB on disk size % improvement Results in previous slides 33% improvement DoubleWrite as the Baseline : :2 :4 :0 :25 :00 :500 :000 Trans/Minute (Higher is Better) Data Written (Lower is Better) DB workload: TPC C (DBT2) DB workload: TPC C (DBT2) Vary Buffer Pool : Database size Atomic Write vs. DoubleWrite 25

26 DB Records Update Ratio 33% improvement DoubleWrite as the Baseline % Reduction 0% 0% 33% 50% 67% 90% 00% Trans/Second (Higher is Better) Data Written (Lower is Better) DB workload: SysBench DB workload: SysBench Vary Update ratio in total workload Atomic Write vs. DoubleWrite 26

27 Conclusions Solid State Storage opens opportunities for higher order primitives in storage interfaces Atomic Write: allows multi block write operations to be completed as an atomic unit Benefit upper layers with ACID requirements OS, Filesystem, DBMS, applications Reduced complexity Improved performance Improved device durability 27

28 Future Work Work with Linux kernel maintainers to integrate atomic write in a non proprietary way To support multiple outstanding atomic write groups Full transactional support Explore other higher order I/O primitives 28

29 Thank You! 29