There are basically two things which I majorly like about using
MyRocks, 1. LSM Advantage – smaller space & lower write
amplification and 2. Best of MySQL like replication,
storage engine centric database infrastructure operations and
MySQL orchestration tools. Facebook built RocksDB as an
embeddable and persistent key-value store with lower
amplification factor () compared to InnoDB. Let me explain a
scenario were InnoDB proves less efficient compared to RocksDB in
SSD:
We know InnoDB is constrained by a fixed compressed page
size. Alignment during fragmentation and compression causes extra
unused space because the leaf nodes are not full. Let’s consider
a InnoDB table with a compressed page size of 8KB. A 16KB
in-memory page compressed to 5KB still uses 8KB on storage.
Adding to this, each entry in the primary key index has 13
bytes of metadata (6 byte transaction id + 7 byte rollback
pointer), and the …
Community journal
Follow the feed
The latest from the MySQL community
Ideas, releases, practical guides, and perspectives from the people building with MySQL.
Showing entries 1 to 1 of 1
« Previous |
Next »
Nov
02
2018