Removing Double-Logging with Passive Data Persistence in LSM-tree based Relational...
summary
Proposes a concrete redesign that removes WAL from storage engine in LSM-tree RDBs, implemented as a MyRocks prototype and evaluated with Linkbench and TPC-C. Introduces a passive flushing policy, an epoch-based persistence scheme, and flash-flag markers to track per-column-family flush progress and enable partial recovery. Claims up to 49.9% throughput improvement, up to 89.3% latency reduction, 42.9% fewer disk I/Os, and recovery time cut by up to 4.8% versus stock MyRocks.
AI-written summary · about
chapters (7)
related talks
52mRocksDB Performance and Reliability Practics
15mADOC: Automatically Harmonizing Dataflow Between Components in Log-Structured Key-Value
35mQuestioning Database Claims: Design Patterns of Storage Engine
29mAccelerating Performance: Mastering RocksDB for High Speed Data Processing
39mAn Introduction to B-trees and LSM-trees for DEVs and DevOps
51mSix New Important RocksDB Features And Planned Works
57mRocksDB
12mSpanDB: A Fast, Cost-Effective LSM-tree Based KV Store on Hybrid Storage