Understanding and tuning WiredTiger
summary
Covers the WiredTiger storage engine introduced in MongoDB 3.0, explaining its architecture (document-level MVCC locking), compression support, and the option between B-tree and LSM indexes. Describes how to tune and monitor WiredTiger for improved performance.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:06Most popular NoSQL database
- 1:235 NoSQL categories
- 2:26MongoDB is a Document Database
- 3:48Operational Database Landscape
- 11:40MongoDB 3.0 Storage Engine API
- 14:11Some existing engines
- 16:18What is Wired Tiger
- 19:54Choosing Wired Tiger at server startup
- 20:26Main tunables exposed as MongoDB options
- 21:41All Wired Tiger options via configString (hidden)
- 23:45Understanding Wired Tiger architecture
- 26:22Covering 90% of your optimization needs
- 27:04fit working set in Cache
- 27:33fit working set in OS Disk Cache
- 29:16Strategy 2
- 29:48SSD disk + compression to save
- 30:16SSD disk (no compression)
- 30:44Compression benchmarks
- 33:11What problem is solved by LSM indexes?
- 36:052B inserts (with 3 secondary indexes)
related talks
01h 03mWiredTiger
28mComparing MongoRocks, WiredTiger and mmapv1 for performance and efficiency
19mMongoDB Engines: Demystified
20mMongoDB size management
47mSchema design for fast applications
51m5 boring performance improvements in MongoDB 3.4 that matter
25mPercona Server for MongoDB: Features Overview
41mWant to turbocharge your database? Ask me how!
