MyRocks at Facebook and a Roadmap

on YouTube ↗12m

" summary

Facebook replaces InnoDB with MyRocks (RocksDB as a MySQL storage engine) for the main activity DB, cutting storage roughly 50% space reduction versus compressed InnoDB while keeping CPU and I/O similar. Migration uses automated clones, continuous consistency checks, and staged replica promotions across 200–300 instances, plus tooling for fast instance creation. Deployment succeeds at scale, frees up shards so capacity halves, and development now targets MySQL 8.0 support and mixed InnoDB/MyRocks deployments and larger 5–50TB instances.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 0:21UDV
3. 2:33MyRocks
4. 3:41Space
5. 5:02Migration
6. 5:48Fast Instance
7. 6:35Second Instance

" related talks

• 50mInnoDB to MyRocks Migration in Main MySQL DatabaseYoshinori Matsunobu · SREcon17 Asia/Australia
• 51mMyRocks deep dive and production deployment at FacebookYoshinori Matsunobu · HighLoad++ Moscow 2018
• 47mLessons Learned from Our Main Database Migrations at FacebookYoshinori Matsunobu · SREcon18 Asia/Australia
• 45mMyRocks Table Engine for MySQLAleksey Maykov, Sergey Petrunya · HighLoad++ 2015
• 52mRocksDB Performance and Reliability PracticsYoshinori Matsunobu · Percona Live 2022
• 27mMyRocks: best practice at Alibaba - MySQL Storage Enginejiayi wang, dengcheng he · Percona Live Open Source Database Conference 2017
• 39mLessons Learned from Our Main Database MigrationsYoshinori Matsunobu · SREcon18 Americas
• 57mRocksDBMark Callaghan, Igor Canadi · The Databaseology Lectures (Fall 2015)