MongoDB Engines: Demystified
summary
MongoDB offers WiredTiger and MMAPv1 plus Percona Server’s MongoRocks and In-Memory, and the talk gives concrete tradeoffs: WiredTiger default since 3.2 with document-level locking, compression and its own memory manager; MMAPv1 delegates memory to the OS and keeps collection-level locks; MongoRocks (LSM) targets write‑heavy workloads with compaction and different I/O patterns; must dump and reload to change an engine on an instance, yet engines can be mixed across replica set members. Demo uses Percona Monitoring and Management.
AI-written summary · about
chapters (13)
- 0:00MongoDB storage engines
- 1:08MMAPv1 history
- 2:34WiredTiger introduction
- 4:30WiredTiger vs MMAPv1
- 5:34Multiple storage engines
- 7:08WiredTiger features
- 9:03WiredTiger encryption
- 11:07In-memory replication
- 12:22RocksDB introduction
- 13:51RocksDB features
- 14:35MMAPv1 legacy
- 15:46Monitoring with PMM
- 17:03Demo and resources
related talks
46mUnderstanding and tuning WiredTiger
46mUnderstanding and tuning WiredTiger
37mThe State of MongoDB, Its Open Source Community, and Where Percona Is Going With It
09mOpen Software for MongoDB Where Percona Fits
45mMongoDB
21mWhy Pay for MongoDB Enterprise When Open Source Has You Covered?
19mReady for the Agentic Era Where Percona for MongoDB Is Going Next
57mRocksDB